How team and access work
Everyone in your organization signs in with their own account. What each person can see and do comes from the roles they hold: on the whole organization, or on one project. A role is given to a person directly, or to a group they belong to. A control you have no role for isn't shown.
This page explains the ideas behind access. For the steps, see Invite a person and grant access, Create a group and Check what someone can access. For every control on the screen, see People, Groups and Your organization.
Terms
| Term | Meaning |
|---|---|
| Organization | Your company's space in Jaah. Its people, groups, projects, credentials and nodes all belong to it. |
| Person | One account in your organization, listed on the People tab. It signs in with its Email. |
| Group | A set of people. Every role a group holds applies to each member. |
| Everyone | The group every person in your organization belongs to. Jaah adds and removes its members. |
| Role | A named set of things a person may do, such as Project Developer. |
| Scope | What a role applies to: the organization, one project, or one model account. |
| Source | How a person holds a role: Direct, Via a group, or Inherited from the organization. |
| Access request | An ask for a role on something you can't open yet. |
The roles
Jaah has five roles. Two apply to the whole organization; three are project roles.
| Role | What it allows |
|---|---|
| Org Owner | Full control of the organization, including who else is an owner. |
| Org Admin | Administers the organization: its projects, people, credentials and settings. |
| Project Maintainer | Runs a project: its settings, worktrees, sessions, schedules and workflows. |
| Project Developer | Works on a project: creates and edits tasks and brings their own credentials. |
| Project Viewer | Reads a project: its tasks, worktrees and sessions. |
Org Owner and Org Admin are granted only on the organization. A project role can be granted on one project, or on the whole organization, where it applies to every project. A project role can also be granted on a model account. Grant a role when you add a person, on their Access tab, or on the Access tab of the organization, project or account.
An organization with an email domain can give a Default role to people who join through it: None, Project Viewer or Project Developer.
Where a role comes from
A person's roles add up from three places:
- Direct — given to the person.
- Via a group — given to a group they're in. Remove them from the group, and the role goes too.
- Inherited from the organization — a role granted on the whole organization reaches each project.
A grant on a project can carry an Expires date; left empty, it never expires. To see every role a person holds and where it comes from, open their Access tab. To ask whether they may do one thing, and why, use Check access.
A person's states
| State | What it means | What moves it on |
|---|---|---|
| Invited | The person is listed, but hasn't accepted the invitation yet. A hollow round mark, and the Account card reads Invited — hasn't accepted yet. Resend invitation sends the email again. Roles can be granted already; they apply on accepting. | The person accepts: from the invitation email, or, if they already use Jaah, from their account menu. |
| Declined | The person turned the invitation down. A Declined tag beside the address, and the Account card reads Declined the invitation. | Invite again sends a new invitation. |
| Activated | The person has signed in. A filled round mark, and the Account card reads Active. | An Org Owner or Admin selects Disable account. |
| Disabled | The person is signed out and can't sign in. A Disabled tag beside the address. | An Org Owner or Admin selects Enable account. |
Deleting an account removes it and every group membership it had.
When you have no access
Opening something you hold no role for shows a No access page with the address you're signed in with. When it's a project, a model account or your organization you can't open, the page offers Request access: pick the Role you need, add a Note (optional), and send it. Only project roles can be requested; Org Owner and Org Admin are only ever granted.
A request is Pending until someone who manages access there, an Org Owner, Org Admin or Project Maintainer, decides. They Approve or Deny it from the Requests tab on the Support page, and it becomes Approved or Denied. You're notified of the decision. Your own requests are in that tab's Mine box. See Support.
Related
- How projects work — what a project role lets you do there.
- How tasks work — the access each task action needs.
- How credentials work — who may add, attach and change a credential.
- Give someone access to a project — grant a role on one project.