Members and Guests
Invite a colleague with a role or a client as a guest of one project, change a member's role, remove someone, and manage the invitations still waiting.
By the end of this page you will know how people get into a team, what the difference between a staff member and a guest is, how to change what a member may do, and how to take someone out again.
Every person in Zuse Bifrost arrives through an invitation. There is no sign-up page: you invite an email address, the address receives a signed link, and following the link creates the account if there is none and adds the person to your team. A colleague joins as staff, with a role that applies across the team. A client stakeholder joins as a guest of one project, sees only what that project shares, and holds no team-wide permissions at all.
Before you begin
| You need | Why |
|---|---|
| To see members | The members page opens for the owner and for members whose role carries team-member:view-any. |
team-member:invite | To send or withdraw invitations. The owner always may. |
team-member:update-role | To move a member to another role. |
team-member:remove | To remove a member. |
| A project in the team, to invite a guest | A guest is invited to one project, so the team needs at least one project before a guest can be asked in. |
Where members live
Open Account Settings → Teams, then choose Members from the row menu of a team. The page has two parts.
Members lists the owner first, then every member by name:
| Column | What it shows |
|---|---|
| Person | Initials, name and email address; your own row is marked (you). |
| Role | Owner for the person who created the team, otherwise the member's role name. |
| Row menu | Change role and Remove from team, shown only for members, and only when your role allows them. |
Pending Invitations lists what has been sent and not yet accepted:
| Column | What it shows |
|---|---|
| The invited address, with the name you typed beneath it when you gave one. | |
| Role | The role offered; for a guest, the project they are invited to. |
| Sent | How long ago, and who sent it. |
| Action | Withdraw, when you may invite. |
Invite a colleague
- Press Invite Someone.
- Type the Email address. Capitalisation and surrounding spaces are ignored; the address is stored in lower case.
- Pick the Role the person will hold. The list holds the team's roles, default and custom; it starts on Developer.
- Optionally type their Name and Job title. Both pre-fill the page where they create their account; neither is required.
- Press Send Invitation.
The invitation appears under Pending Invitations, and an email with the acceptance link is on its way. The page refuses, with a message, when the address already belongs to the owner or a member of the team, when an invitation to it is already pending (withdraw that one to send another), and when the role is not one of the team's.
Invite a client as a guest
- Press Invite Someone and type the client's Email.
- Pick Guest as the Role. A Project field appears.
- Choose the Project the client is invited to. Only the team's live projects are offered.
- Add their Name and Job title if you know them; the title is recorded on their project membership as well.
- Press Send Invitation.
A guest invitation without a project is refused, as is a project that belongs to another team. When the guest accepts, two things happen at once: they join the team under the guest role, which carries no team permissions, and a project membership is written that marks them as external to the team and gives them the guest view of that one project.
A guest exists only on the projects they were invited to. They see the approved artefacts, the approvals that name them, their own tickets and the releases and incident status those projects share; estimates, time, internal comments, repositories and the other projects of the team stay hidden.
What the invitee receives
The email is titled You are invited to <team> on ZuseGenius. It names the role and, for a guest, the project, and carries one button, Accept the invitation, whose link is signed: it works only as sent, and only until the invitation is accepted or withdrawn. Accepting an invitation describes what the person sees next, which depends on whether they already hold an account.
A new address gets the only sign-up form in Zuse Bifrost: their name, pre-filled from your invitation, and a password. The account starts verified, because the signed link reached the inbox.
An existing account, signed out, is sent to sign in; the sign-in completes the acceptance.
The invitee, already signed in, joins the moment the link opens.
Withdraw an invitation
- Under Pending Invitations, press Withdraw on the row.
- The row disappears and the link in that email stops working at once; whoever follows it is told the invitation is no longer valid.
Nothing is announced for a withdrawal, because nobody joined. Send a fresh invitation if you change your mind.
Change a member's role
- Open the member's row menu and choose Change role. The dialog opens on their current role.
- Pick the new Role and press Save.
- The new role applies the next time the member loads a page; nothing they have open is interrupted.
Choosing the role they already hold saves and announces nothing. The owner has no role to change: ownership is not a role, and it stays with the person who created the team.
Remove a member
- Open the member's row menu and choose Remove from team.
- Press Remove in the confirmation.
- They lose access to the team and its projects at once. If the team was their current one, they are pointed at another team of theirs, or at none. Their project memberships, comments and work stay as history.
The owner cannot be removed. To take a guest off one project while leaving them in the team, use the project's own membership page when it lands; today a guest is removed from the team as a whole.
All the fields
What happens next
| Action | Event announced | Payload |
|---|---|---|
| Invitation sent | team.member_invited | The address, the invitation id, the role code and the team. |
| Invitation accepted | team.member_joined | The role code, the team and the new member's user id. |
| Guest accepted | team.member_joined and project.member_added | The project event marks the membership as external, role guest. |
| Role changed | team.member_role_changed | The previous and the new role code. |
| Member removed | team.member_removed | The team and the user id. |
| Invitation withdrawn | nothing | Nobody joined, so there is nothing to announce. |
Permissions
| Action | Who may do it |
|---|---|
| Open the members page | The owner, or a member with team-member:view-any |
| Invite and withdraw | The owner, or a member with team-member:invite |
| Change a member's role | The owner, or a member with team-member:update-role |
| Remove a member | The owner, or a member with team-member:remove |
| Change or remove the owner | Nobody |
Buttons you are not allowed to use are not shown, and the action behind each one checks again when it runs.
Frequently asked
Related
- Teams: where the members page is opened from.
- Roles: what each role lets a member do.
- Accepting an invitation: the page the link opens.
How is this guide?
Last updated on