Invite people and choose what they reach
Invite a person to the organization, give them a role and the projects they reach, then change or end their access on the members page.
4 min read
A member is a person of the organization with a role. This page is about the members page of the console: invitations, the role of a member, the projects a member reaches, and removal.
Where the members are
Open Settings, then Members. The page has two tabs, Members and Invitations. It lists the people of the whole organization, whatever project is chosen in the header.
A row of a member shows the name, the email, the role, the project access and the date the person joined.
The page opens for whoever has the management:read permission. The team is managed by a signed-in person with the management:write permission, which the roles Owner and Admin have. An API key cannot invite, change or remove a member.
Who may grant a role
Organizations, projects and roles says what each role may do. Two rules decide who gives a role to whom.
An owner acts on every member and grants every role.
An admin acts on every member except an owner and grants every role except Owner.
The same rules hold for an invitation: only an owner invites an owner, and only an owner resends or revokes that invitation.
Invite a person
1. Start the invitation
Press Invite.
2. Enter the email
Type the address of the person. The invitation is valid for that address only.
3. Choose the role
The list holds the roles you may grant. It starts at Developer.
4. Choose the projects
Under Project access choose All projects or Selected projects, and tick the projects. An owner and an admin always reach every project, so for those two roles the choice is locked.
5. Send the invitation
Press Send invitation. Slen mails a link to the address, and the invitation appears on the Invitations tab as Pending.
An invitation is valid for 7 days. A person who is already a member cannot be invited, and an address holds one open invitation to an organization at a time.
How the person accepts
The person follows the link in the mail and signs in, or signs up, with the invited address. Someone who already has an account with that address also finds the invitation on Organizations, above the list of organizations, with Accept and Decline. Either way, the email of the account has to be confirmed first.
Accepting makes the person a member with the role and the projects of the invitation, and opens the organization for them.
Manage an invitation
The Invitations tab lists the invitations that are open, Pending or Expired. An invitation that was accepted, declined or revoked leaves the list.
| Action | What it does |
|---|---|
| Resend | Mails a new link. The previous link stops working, and the 7 days start again. Within a minute of the last mail nothing is sent |
| Revoke | Closes the invitation. The link in the mail stops working at once |
| Invite again | Offered for an expired invitation. Opens a new invitation filled in with the address, the role and the projects of the old one |
Change a role or the projects
Open the menu in the row of the member and choose Change role and access. Choose the role and the project access, then press Save.
You cannot change your own membership. The menu in your own row offers only Leave organization.
An organization keeps at least one owner. The last owner cannot be given another role, be removed or leave until somebody else is an owner.
A member who becomes an owner or an admin reaches every project from then on.
Remove a member
Open the menu in the row of the member, choose Remove from organization and confirm with Remove. The access of the person ends at once. The flows, the keys and the data of the projects stay.
Three things happen with the removal.
The open invitations the person sent are revoked.
The API keys the person issued keep working unless you tick Revoke the API keys this member issued.
The person leaves the routes of notifications, and their subscriptions to notifications in the organization are removed. A route that named only this person is deleted.
A key that is revoked stops working at once. Before you tick the box, check that no service still sends a key this person issued.
Leave an organization
Open the menu in your own row and choose Leave organization. You lose access to its projects, flows and keys at once, and only a new invitation brings you back.
Who sets up notifications
The role also decides who sets up the notifications of the organization. An Owner or an Admin, signed in as a person, connects the channels of the team in Slack, Microsoft Teams, Discord and Telegram and writes the routes that say who hears about what. A channel or a route of the whole organization needs access to every project. A route that names a role reaches whoever has the role when an event comes, and a member whose role changes gets the subscriptions recommended for the new role. Each member chooses their own email, Telegram and quiet hours. See Notifications.
Where to go next
Organizations, projects and roles — what each role sees and how to switch the project.
Manage API keys — issue and revoke the keys of a project.
Audit log — who invited, changed or removed a member.
Notifications — who hears about alerts and approvals, and where.