Members

Who sees the screen

NeedsView view

A member who holds View can open Members from the left rail. A member whose roles grant no View has no link. If they type the address, the product shows the not-found page.

What the screen offers depends on whether you hold Manage the organization. A member who holds it is an administrator.

• An administrator reads: Everybody in this organization. Click a role to grant or revoke it — grants add up, so somebody can hold several. Team membership is managed on the team. The role chips are buttons, each row has Remove, and Pending invitations sits below the table.
• Everybody else reads: Everybody in this organization, the roles they hold and the teams they are on. Only an administrator can change roles. The chips are labels, and the screen has no buttons.

The table

The table has one row per member, in order of display name. A deleted account is absent from the table.

Person

The display name, with the email address under it. Your own row carries the badge you.

Roles

One chip per organization role. An administrator sees every organization role. A chip is full when the person holds that role. Everybody else sees only the roles the person holds. Team roles and the Product Owner role are never in this column.

Teams

One chip per Scrum Team the person is on, with their slot: Scrum Master or Developer. A person on no team shows —. The column is read-only. To change it, open the team. See Scrum Teams.

Grant a role

NeedsManage the organization org_manage

1. Find the person's row.
2. In Roles, click an empty chip.

The chip fills at once, and the product saves the grant. The product disables the chip until the save answers, so a second click does nothing.

One chip is one grant. To give several roles, click several chips. A person with two roles can do what either role allows. The person holds the new role everywhere in the organization from that moment.

A project override is the one exception. On one project it can allow or refuse one capability for one person, whatever their roles grant. See Project overrides.

You can grant only organization roles here. A person holds a team role through a Scrum Team, and the Product Owner role through a project. See Roles and permissions.

The product records each time somebody grants or revokes a role, on the Activity screen. The screen shows the time, the name of the person who made the change and the event type. It does not show which member or which role. See The activity feed.

If the product refuses a grant, the chip empties again and a message appears above the table.

Revoke a role

NeedsManage the organization org_manage

1. Find the person's row.
2. In Roles, click a filled chip.

The chip empties at once, and the person loses the role everywhere in the organization. The product disables the chip until the save answers. If the product refuses, the chip fills again and a message appears above the table.

Other messages above the table

The product can also refuse when you grant or revoke a role, because your page is out of date, or because the request did not arrive. Each message names the cause.

Role not found.

Somebody deleted the role after your page loaded.

That person is not a member of this organization.

Somebody removed the person after your page loaded.

That person does not hold this role.

Somebody else revoked the role after your page loaded.

You do not have permission to perform this action.

You no longer hold Manage the organization. Somebody revoked it after your page loaded.

Too many requests.

You sent too many changes in a short time. Wait a moment. Then try again.

Could not reach the server. Check your connection and try again.

The request did not reach the product. Check your connection. Then try again.

After any of these, reload the page. The table then shows the current state.

The last administrator

No one member owns the organization. The product protects the capability Manage the organization instead. At least one member must hold it at all times, through an organization role. The same grant on a team role or on the Product Owner role does nothing at organization level, so it does not count. Three changes can break the rule, and the product blocks each one with the same message: This would leave nobody able to manage the organization. Give somebody else "Manage org" first.

• You revoke the last organization role that grants it, on this screen.
• You remove the last member who holds it, on this screen.
• You untick it on the last organization role that grants it, on the Roles screen. See Roles and permissions.

The role named Owner is not special on this screen. You can revoke it like any other role, as long as somebody still holds Manage the organization. A person who holds it through two roles counts once.

Remove a member

NeedsManage the organization org_manage

1. Click Remove at the end of the person's row.
2. Read the dialog Remove … from the organization?
3. Click Remove from organization.

To keep the person, click Cancel. The Escape key and the close button of the dialog do the same. Each closes the dialog and removes nobody. A click outside the dialog does not close it.

The dialog names the person in place of the dots. It says what the removal does: They lose their roles, their team memberships, and any project overrides. Re-inviting them later starts from that invitation alone — none of this comes back. On your own row it adds This is your own account.

While the request is out, the button reads Removing… and the product disables Cancel. On success the dialog closes and the table reloads. If the product refuses, the message appears inside the dialog, and the dialog stays open.

What blocks a removal

The screen always offers the button. The product refuses after you confirm, and the message appears in the dialog. Three rules block a removal.

To promote another member to Scrum Master, open the team. Then set their Slot to Scrum Master. That save makes the current Scrum Master a Developer, so there is nothing to change first. The control needs Manage the organization. See Scrum Teams.

The dialog can also show the messages from the list above:

• That person is not a member of this organization.
• You do not have permission to perform this action.
• Too many requests.
• Could not reach the server. Check your connection and try again.

The causes are the ones under the other messages, above.

What happens to their work

Only the membership goes. The account stays, and the person keeps every other organization they are in.

• Their access ends at once. The organization leaves their list, and its pages show as not found for them.
• The product deletes their roles, their team memberships and every project override on them. An override they set for somebody else stays. See Project overrides.
• Their name stays on everything they wrote: items, item history, notes, the Activity screen, and every override they set for somebody else. The product does not change those records.
• An item that names them as the assignee keeps their name.
• They stay on the Attendees list of every Scrum Event they were invited to, with their capacity and their attendance. See Scrum Events.
• Invitations they sent stay pending. Under Invited by, those rows now read A former member.
• Their seat is free. On a paid plan the subscription quantity drops with it. See Plans and billing.
• The product records the removal on the Activity screen, as org.member_removed. The screen does not show the name or the email address of the person removed. See The activity feed.

If you invite them again, they start with the roles on that invitation and nothing more. The product restores nothing from before.

Remove yourself

NeedsManage the organization org_manage

There is no separate control to leave an organization. Use Remove on your own row. The dialog marks it with This is your own account. The product blocks it when you are the last administrator, so you cannot leave an organization of one.

After the product removes you, the table does not come back. The organization leaves your list, and the product shows the not-found page.

Pending invitations

NeedsManage the organization org_manage

Below the table sits the section Pending invitations, with the note People who have been invited but have not joined yet. Only outstanding invitations appear here. The section is absent unless you are an administrator.

When no invitation is pending, it reads Nobody is waiting to join. Use Invite someone to send an invitation. Otherwise it is a table, oldest invitation first, with one row per address.

Address

The email address that the invitation went to.

Roles on joining

The organization roles the person receives when they accept. A role that somebody deleted since then shows as Unknown role.

Invited by

The display name of the member who sent it, or A former member.

Expires

The date and time after which the link is no longer valid, in your own timezone.

The section holds three controls: Invite someone at the right of the heading, and Resend and Revoke on each row. A person joins the organization only through an invitation. Nothing on this screen adds a member directly. To read the whole path, from the email to the moment somebody accepts, see Invitations.

What the screen does not do

• It does not grant team roles or the Product Owner role. A person holds those through a team and a project.
• It does not tell a person that their roles changed. The product sends no notification. The change appears on the Activity screen only, for an administrator to read.
• It does not show which role gives a capability. To read what each role allows, open Roles and permissions.