Invite people and set roles
Orbit has two independent layers of roles.
| Layer | Roles | What it decides |
|---|---|---|
| Site | administrator (admin), member, viewer |
What a person can do across the whole site. Global configuration and user invitations need a site administrator. |
| Project | administrator, member, viewer | What a person can do in one project. A viewer cannot write project data. Project administrators manage memberships, workflows, automations and project custom fields. |
Project roles are independent of the site role. A person’s effective role in a project is the strongest of their own role and the roles of the groups they belong to.
The last usable site administrator cannot be demoted or disabled.
Invite someone to a project
Section titled “Invite someone to a project”Project administrators invite people by e-mail.
- Enter the e-mail address and choose a role: administrator, member or viewer. The default is member.
- Choose how long the invitation is valid, from 1 to 30 days (7 by default).
- Orbit mails a link. The person opens it, signs in with the matching account or creates one, and joins the project.
You can resend an invitation, which gives a new link and makes the old one stop working, or revoke it until it is accepted. A list shows each invitation as pending, expired, revoked or accepted, who sent it and how often it was resent.
An invitation never grants more than the inviter holds. The role granted is the weaker of the role offered and the inviter’s current project role. If the address already has that role or more, or an invitation to it is pending, Orbit refuses the new one.
Guests
Section titled “Guests”When a project administrator invites someone who is not yet on the site, that person joins as a guest of the project. Guests see only the projects they are invited to and the people in those projects, and they cannot create site-wide objects such as projects, plans, teams or templates. Direct links cannot take a guest outside their projects.
Who may open Code / CI, Observability, Knowledge and Lumen
Section titled “Who may open Code / CI, Observability, Knowledge and Lumen”Access to Forge, Pulse, Folio and Lumen is chosen per person by a site administrator in the people directory. A person without a product is refused at the web proxy, even if they hold a project role. Site administrators always have every product. See People, groups, guests and product access.
Deactivate a person
Section titled “Deactivate a person”A site administrator can deactivate a person and reactivate them later. A deactivated person cannot sign in, and their sessions are refused. Their history stays: authorship on work items, comments and history is kept, and team references survive.
Site administrators
Section titled “Site administrators”A site administrator is invited separately, by e-mail, with an organization role. See Organizations, sites and roles.