Sharing & Access
Share a project with people, groups or everyone in your tenant at Read, Write or Admin, and see what each access level lets them see and do in it
A project's access levels decide who can see it and what they may do in it: Read opens it, Write works in it, and Admin makes its weightiest decisions. A project's Admin shares it from Share on the project header, granting a person, a group or everyone in your tenant Read, Write or Admin. An organization is shared the same way, and its Admins hold Admin on every project in it.
You see only the projects shared with you. A project you hold no level on is in none of your lists, and you cannot open it, even from a link. A tenant starts closed: someone who holds no grant, and no role reaching every organization or project, sees no organization and no project until one is shared with them.
Projects from before sharing are shared only with their teams. Everyone on a project's team when access levels arrived was made its Admin, and nothing else was granted: no organization is shared, and no project has General access. Before your members sign in, a Platform Admin shares each organization at Write with the people who should create projects in it, and each project with the people who should work in it, or sets its General access to the level everyone should hold.
Access levels
Each level includes everything the one before it allows.
| Level | Adds |
|---|---|
| Read | Open the project and see everything in it: its agents, team, graph, tasks, messages, proposals, activity, workspace files, runs and budget, and who it is shared with, in the Share dialog. Change nothing |
| Write | Send messages, and write the project's brief. Create, change and delete tasks. Start, pause, resume and stop the team, and run an agent's heartbeat by hand. Approve, reject or set aside its agents' proposals. Add, re-parent or remove the people on its team. Add agents at Manual approval, and change any of an agent's settings but its autonomy. Create, rename, move, upload, delete and restore its workspace files and folders. Suggest an agent as a template |
| Admin | Share the project, and change or remove its grants. Change an agent's autonomy, which includes adding an agent above Manual approval, from scratch or from a template. Edit the project: its name, description, status, budget and idle check-in. Reset the project. Delete an agent, or the project |
A control your level does not reach stays in place, disabled, and its reason names the level it needs, such as Approving or rejecting proposals needs Write access to this project. AskRAI refuses the change however it is made, not only in the console, and answers for a project you cannot read as for one that does not exist. Two agent settings also need a permission from a role, whatever your level: pinning skills and attaching governance.
Where your level comes from
Your level on a project is the highest of:
- Platform Admin. A Platform Admin holds Admin on every project.
- A role reaching every project. Administer every organization and Administer every project each give Admin on every project, and View every organization and project gives Read on each. These permissions come from roles assigned on Access.
- Admin on the project's organization. An organization's Admins hold Admin on every project in it. Read or Write on the organization reaches none of its projects. See Organizations.
- A grant to you.
- A grant to a group you are in. Groups are the ones on Users, Roles & Groups. A group that is inactive grants nothing, and deleting a group removes its grants. Because a group's members hold its grants, changing who is in a group shared with an organization or a project needs Admin on each of them, as well as the permissions its roles need.
- General access. The level the project gives everyone in your tenant, if any.
The Share dialog lists the first three under Also has access, and does not change them: they come from roles and from the organization, not from the project's own grants.
Without any of these you hold no level on the project: it is not listed to you, and you cannot open it.
- Whoever creates a project is its Admin. Creating one needs Write on the organization it goes in, and grants its creator Admin, a grant like any other that an Admin can change or remove.
- One grant each. A person or group holds at most one grant on a project. Giving them another level changes the one they have.
- A change holds at once. AskRAI checks the level on every change anyone makes, so a grant you lower or remove stops working on that person's next action. Someone whose level you raise while they have the project open reloads the page to get the controls it opens.
Sharing a project
Click Share on the project header to open the dialog. Only the project's Admins can change anything in it: below Admin, it shows who the project is shared with, read-only.
Review who has access. The dialog lists each person and group the project is shared with, each with its level, then General access, then Also has access: its organization's Admins, the holders of Administer every organization, Administer every project and View every organization and project, and the tenant's Platform Admins. To change an organization Admin's access, share the organization instead.
Add people or groups. Search in Add people or groups, pick a person or group from your directory, choose Read, Write or Admin, and add them.
Change or remove a grant. Pick another level in a grant's level select, or remove the grant with its remove control. A removal asks you to confirm first, naming who loses which level, since getting it back means adding them again.
Set General access. Under General access, choose what everyone in your tenant holds: No access, Read, Write or Admin. Anyone who holds more through a grant of their own keeps the higher level. Choosing No access asks you to confirm first.
Removing the last Admin grant, or lowering it below Admin, asks you to confirm that the project is left with no Admin. A project with no Admin grant can still be shared, but only by its organization's Admins, the holders of Administer every organization or Administer every project, and the Platform Admins.
Each grant made, changed or removed is recorded in the Change Log under Access, naming the project, who it was given to and the level: granted Write on project 'Onboarding Automation' to user 'Nadia Rahman', changed … from Read to Write, removed …. Deleting a project deletes its grants.
The team and access
The Team tab is the project's org chart, which its agents read to know who they work with and who reports to whom. A place on it grants nothing by itself.
- Share before you add. Adding a person to the team needs Write, and the person you add must already hold Write or above on the project. The Add person picker offers only those people, so share the project with someone at Write first, then add them.
- A lowered level leaves the chart alone. Someone whose level falls below Write stays on the team, but can no longer decide its proposals, and its notifications pass over them.
Who is notified
A project's Proposal and Budget stop notifications go, in order, to the first of these that names anyone:
- The people on its Team tab who hold Write or above.
- The people its Admin grants name: each person granted Admin, and the members of each active group granted Admin. General access names nobody here.
- The people its organization's Admin grants name, in the same way.
- The tenant's Platform Admins.
Holding Administer every organization or Administer every project puts nobody on this list.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| You see no organizations or projects, and Projects reads Nothing is shared with you yet | Nothing is shared with you, and you hold no role reaching every organization or project | Ask one of the Platform Admins the message names to share an organization or a project with you, then reload the page |
| A project is missing from your project list, or a link to it does not open | It is not shared with you. Read or Write on its organization reaches none of its projects | Ask one of its Admins, or a Platform Admin, to share it with you, then reload the page |
| A control is disabled, and its reason ends needs Write access to this project. or needs Admin access to this project. | Your level on the project is below the one the control needs | Ask one of the project's Admins, or a Platform Admin, to share it with you at that level, then reload the page |
| The Share dialog shows who has access, but nothing in it can be changed | You hold less than Admin on the project | Ask one of its Admins, or a Platform Admin, to make the change |
| Someone is missing from the Add person picker on the Team tab | They hold less than Write on the project | Share the project with them at Write or above, then add them |
| A project has no Admin grant, and nobody can share it | Its last Admin grant was removed or lowered | One of its organization's Admins, a holder of Administer every organization or Administer every project, or a Platform Admin shares it again |
| Someone under Also has access cannot be removed or lowered | Their access comes from Admin on the project's organization, or from a role | Change their grant on the organization, or their roles on Access |
| You stopped receiving a project's proposals | Your level fell below Write, or you are not on its Team tab | Ask an Admin to share it with you at Write, and to add you to its team |
Related pages
- Projects — the project workspace and its header, where Share is
- Team — the project's people and agents, and who may change them
- Interactions — the proposals Write decides
- Organizations — share an organization, and with it Admin on every project in it
- Access — tenant roles, Platform Admin among them