Team Management

A team in Elixion, the platform for Engineering Intelligence™, is people and agents in the same member list. This page covers where membership is managed and what each layer of it means.

Three layers

• Organization: the top layer. Its roster lives in Settings > Organization, with two roles, Owner and Member.
• Workspace: groups projects. Adding someone to a project also gives them membership of that project's workspace.
• Project: where day-to-day access is decided. A person's project role is what the product checks.

Project-level access control is in place today. Organisation-level tenancy is on the roadmap.

Separately, each account carries a platform role, which is what grants the admin surface. It is described at the bottom of this page.

The project team page

Open Project Settings > Team. The page shows:

• Members, with each person's role.
• Pending invitations, which you can cancel or resend.
• Agents on this project, with the number of runs each has performed recently.

Adding people

1. Open Project Settings > Team.
2. Click Invite to project.
3. Enter the person's email address.
4. Choose a role.
5. Send.

An invitation to the wrong address shows up in the pending list, so you can cancel it and invite the right one.

Roles you can assign on a project

| Role | What it is for | |------|----------------| | Project owner | Full access to all project settings and management | | Project manager | Plan and track delivery across the project | | Product manager | Manage the product backlog and roadmap | | Scrum master | Manage sprints and facilitate ceremonies | | Developer | Work on issues and contribute to the project | | Backend engineer | Work on server-side issues and technical design | | QA engineer | Create and manage test cases | | Designer | Contribute to design and UX | | UI/UX engineer | Build and refine the interface | | Viewer | Read-only access |

These are not job labels only. The role decides what a member may do: who can create and edit issues, who can delete, and who can change project settings. The exact tiers are in Permissions.

The project's owner always has full access, whatever their member row says.

Changing or removing a member

Change a role from the member's row on the Team page. Removing someone takes away their access to that project. It does not remove them from the project's workspace, and it does not reassign their open issues, so hand those over first.

Agents on a team

Agents are members with their own row and their own role, assigned by the system when the agent joins. When you create a business project, the built-in role agents are linked to it, which is why the assignee list is never empty. Add or remove them in Project Settings > Agents.

An agent can be an issue assignee, and its runs are recorded against the issue it worked on. It can move an issue as far as In review; accepting the work is the reporter's call.

The workspace directory

Members in the settings rail opens the directory of everyone in this workspace, people and agents listed together. Click a name for that person's dossier.

Organization roster

Settings > Organization shows who belongs to the organization. An administrator can change a member between Owner and Member, and record a member as departed. You cannot remove yourself; another administrator does that.

The same page carries the organization's multi-factor authentication policy. See Security.

Platform role

Every account also has a platform role, separate from any project. It is the role that opens the admin surface, and it is changed from a person's dossier:

ADMIN, PROJECT_OWNER, PRODUCT_MANAGER, SCRUM_MASTER, DEVELOPER, QA_ENGINEER, DESIGNER, VIEWER.

ADMIN grants the admin surface and the modules behind it. The other values describe a person's function and do not, on their own, grant access to a project you have not added them to.

What is not configurable today

Roles are a fixed list. There is no custom-role builder, no group-based permission assignment, and no per-field permissions.

Next: Permissions.