- Guide
- Collaborating
- Set roles and access
Set Roles and Access
Each team sets who can do what from its pages in Admin. These cover everyone's team role, the switches that change what a whole role may do, who approves each kind of record, the things given to one person by name, and who opens each project. Everyone on the team can read these pages, and the team's Owner changes most of what's on them.
Where Access Is Set
Open Admin from your account menu, where it sits below Settings with the team it opens named beside it. On a phone, Admin is the row after Settings on the You tab. You can also press Manage team on the team's page, or search for Admin, Invite people or Roles and permissions.
The button at the top of Admin's sidebar shows the team you're looking at. Its menu starts with Find a team…, lists the organizations you administer under Organization, then your teams under Teams you help run and Member of, and ends with New team. Picking another team keeps you on the same page.
| Page | What it holds |
|---|---|
| People | Everyone in the team with their team role, anything they hold beyond it, and how many projects they open, then the invitations nobody has answered yet. Click a person to open their page. |
| Projects | Each project with its lead and its people. Click a project to see everyone who opens it. |
| Roles and permissions | What each team role can do, and how long Trash keeps things |
| Approvals | Who approves each kind of record, and the order approval amount |
| Workspaces | Which workspaces the team uses |
| AI and API access | The AI assistants and API keys that reach the team's projects, with a switch for each kind. See Control access for your team. |
| Security | Whether the team requires two-factor sign-in, and who has it on, and whether BLAST can send sequences to NCBI. See Require two-factor sign-in and Turn BLAST off for the team. |
| Plan and seats | The team's plan, compute usage and cloud storage. See Plans and billing. |
| Access changes | Every change to who is on the team and what they can do. See See who changed what. |
An organization admin who picks an organization sees Teams and units, Admins and Plan and billing instead. See Group teams in an organization.
On a phone, Admin opens on a list of these pages. Tap one to open it, and the back arrow returns to the list.
Invite people, at the top of People, opens the invite form. See Inviting to a team.
The Four Roles
| Team role | Who it's for |
|---|---|
| Owner | The one person who holds everything. Only the Owner changes roles and access, and the plan, billing and seats. |
| Admin | The people who run the group. An Admin opens every project, invites and removes people, and manages each project's members. |
| Operations manager | Whoever runs stock, orders, instruments and suppliers. An Operations manager works in Inventory and Orders in every project, manages Facility, approves orders, and creates projects. |
| Member | Everyone else. A Member opens the projects they're added to. |
A team has exactly one Owner. Ownership is handed over from the team's page, never picked as a role. See Transferring team ownership.
Changing Someone's Role
- Open People in Admin and click the person
- Under Team role, pick Admin, Operations manager or Member
Clicking someone's role on the team's page opens the same page.
What Each Role Can Do
Roles and permissions lays the team's permissions out as a table, one column per role with how many people hold it, and one row per permission. Under each row's name, a line says what it covers. Approvals uses the same table. The key above the table says what a cell shows, which is one of five things.
| Cell | Means |
|---|---|
| A check | Everyone in the role holds it |
| A dash | Nobody in the role holds it |
| A switch | Everyone in the role holds it while it's on. The Owner turns it on or off for the whole role. On a row the Owner can name people for, a count sits beside a switch that's off. |
| A count, such as 2 people | Nobody in the role holds it except the people the Owner names one at a time. While nobody is named, the Owner sees Add people. See Give someone access beyond their role. |
| A few words, such as Projects they're added to | It depends on the project |
Every team starts with this table.
| Row | Owner | Admin | Operations manager | Member |
|---|---|---|---|---|
| Invite and remove people | Yes | Yes | Switch, starts off | No |
| Change roles and access | Yes | No | No | No |
| Plan, billing and seats | Yes | No | No | No |
| Open projects | All projects | All projects | Inventory and Orders in all | Projects they're added to |
| Create projects | Yes | Yes | Yes | Switch, starts off |
| Manage a project's members | Yes | Yes | No | Projects they lead |
| Manage Facility | Yes | Yes | Yes | By name |
| Edit suppliers and contacts | Yes | Yes | Yes | Switch, starts on |
| Edit the data dictionary | Yes | Yes | Yes | Switch, starts on |
| Export project data | Yes | Yes | Yes | Switch, starts on |
| Use AI assistants and API keys | Yes | Yes | Yes | Switch, starts on |
Some of the rows cover the following.
- Manage Facility is changing an instrument's booking rules, scheduling downtime, posting notices, keeping the service log, canceling inside the cancellation cutoff, and changing or canceling a teammate's booking or QC run. Adding and editing freezers, rooms and other locations is open to every member. See Lab storage and instruments.
- Inventory and Orders in all means an Operations manager works in Inventory and Orders in every project on the team. Those projects are in their project picker. Everywhere else they work only in the projects they're added to.
- Edit suppliers and contacts covers every change in Contacts. Turned off for Members, they can still read it.
- Edit the data dictionary covers adding, changing, archiving and deleting the fields in the team's Data dictionary. Turned off for Members, they can still pick its fields in a protocol.
- Export project data turned off for Members means an export one of them asks for is refused, with a message saying the team has turned exporting off.
- Use AI assistants and API keys turned off for Members stops their AI assistants and API keys, and any agent a Member runs, from reaching the team's projects. The switches that turn off each kind for the whole team are on AI and API access. See Control access for your team.
On a phone, each row reads as one line saying who holds it, such as Owner, Admins, 3 named members. Tap a row to open it on its own page, with each role's switch and the people the Owner can name.
Choose Who Approves Each Record
Approvals has a row for each kind of record, under Protocols, Notes, Data and figures, Samples and sequences and Stock, orders and Facility. A role whose cell is on can approve, ask for changes on and reject that kind of record. Every role starts on, except Orders for Members.
| Row | Owner | Admin | Operations manager | Member |
|---|---|---|---|---|
| Each kind of record, such as Protocols or Samples | Yes | Switch, starts on | Switch, starts on | Switch, starts on |
| Orders | Yes | Switch, starts on | Yes | By name |
| Controlled-substance requests | Yes | Switch, starts on | Switch, starts on | Switch, starts on |
To leave protocols to the PI, turn Protocols off for Admins, Operations managers and Members, then press Add people beside the Members switch and check the PI. Someone on a project who isn't on the team follows the Member column.
- Orders matters once the team sets an order approval amount, which sits under it. See Approving orders over an amount.
- Controlled-substance requests covers approving and denying a held request on a controlled substance, and approving a request to lower or clear its class. For a lab with a DEA registration, turn it off for the roles that should not approve and name the registrant's designees. See Reviewing a request.
Give Someone Access Beyond Their Role
Manage Facility on Roles and permissions can be given to one person without changing their role, and so can every row on Approvals.
The count in a role's cell, such as 2 people, or Add people while nobody is named, opens a list of the people in that role. The ones already named are checked at the top. Search for someone and check them to give it to them, or uncheck them to take it back.
Naming someone tells them with a notification on their phone, naming what they can now do. What someone holds by name shows in the Access beyond the role column on People.
Tip: To let one Member run the instruments without making them an Operations manager, name them for Manage Facility.
Approving Orders Over an Amount
The Owner sets this under Orders on Approvals. Turn on Hold orders over a set amount for an approver, enter the Amount, pick the Currency, and press Save. Everyone else sees it as it's set.
From then on, an order whose total is at or over that amount in that currency stays in Requested or Incomplete until someone who can approve orders moves it on.
- They can move it to Processing or Complete themselves.
- They can approve it from the order's comment thread, and then anyone who can edit the project can move it.
- Changing what was requested after the approval, such as the quantity or the price, cancels the approval, so someone has to approve the new request before the order moves on.
- Once an order is in Processing or Complete, only someone who can approve orders can change what was requested while its total is at or over the amount. Anyone else moves it back to Requested to change it, and it needs an approval again to move on.
- An approver who rejects it or asks for changes holds it too.
Anyone else who tries to move it reads a message naming the amount and saying someone who can approve orders has to sign off. An order in another currency, or with no price, isn't held. Work with suppliers covers asking for a sign-off.
Set How Long Trash Keeps Things
The Trash row on Roles and permissions, under Data, sets how long trashed items stay and who can remove one before then. The Owner picks one of three levels, and everyone else sees it as it's set.
| Level | Trash clears | Who can remove an item sooner, or empty Trash |
|---|---|---|
| Standard (where every team starts) | After 30 days | The person who trashed it, or the project's lead |
| Leads only | After 30 days | The team's Owner and Admins, and the project's lead |
| Keep all | Never. Items trashed from then on stay until someone restores them | The Owner, who gives a reason each time, which Access changes lists |
Switching to Keep all, or away from it, asks first. Kept items go on counting toward the team's storage, and when the team switches away, everything in Trash gets 30 days from that day.
Moving work to Trash and restoring it stay open to everyone who can edit, whatever the level. See Delete and restore.
Turn a Workspace Off for the Team
Workspaces in Admin lists every workspace grouped as the sidebar groups them, each with what it holds and how much of it the team has across its projects. The Owner unchecks one to turn it off for everyone on the team.
- It leaves the sidebar, the phone home screen and search for everyone on the team.
- Its records stay, and a link to one still opens it.
- Its row says who turned it off and when, and how many of its records stay.
- Checking it again brings it back with everything in it.
Notebook reads Always on, because protocols, protocol runs and every note live in it.
Turning Bench off also takes its tools off the phone home screen. Turning Planner or Facility off takes its panel off Bench.
Anyone can also hide a workspace from their own sidebar in Settings → General, which leaves it as it is for everyone else.
See Who Opens a Project
A project opens to the people added to it and to the team's Owner and Admins. A project's page in Admin and its Project Members dialog box list everyone who can open it, in two parts.
- Added to this project lists its lead and the people added to it, each with their project role
- Owners and admins lists the people who open every project in the team from their role
Project roles covers what View only and Editor can do.
Require Two-Factor Sign-In
An Owner or Admin requires two-factor sign-in from Security in Admin by turning on Require two-factor sign-in. You need it on for your own account first. If you don't have it, turning the switch on takes you through setting it up, then on to the confirmation. The confirmation names who doesn't have it yet and the date they have until.
- Who it covers is everyone in the team, guests on its projects and its projects' leads. Each has a week from when you turn it on, or from when they join if that's later, and a notice at the top of the app shows them the time
- After the week, Conspecta opens to a set-up screen for anyone still without it, and their API keys, AI assistants and agents stop until they set it up. Members can leave the team from that screen
- The page lists everyone in the team, those without two-factor first, each marked On, Not set up or Overdue
- Turning it off lifts the requirement at once. Each change is listed under Rules in Access changes
Turn BLAST Off for the Team
A BLAST search sends the sequence itself to NCBI's public servers. The Owner turns BLAST off for every project in the team from Security in Admin by clearing Allow BLAST against NCBI. Admins see the setting and can't change it.
- While it's off, the BLAST dialog and the BLAST Search step of Add Sequence say so, and Search stays unavailable. A connected AI assistant or an API key is refused too
- Still on are searching NCBI and UniProt by keyword and adding a published sequence by accession, which send only the words or the accession
- Each change is listed under Rules in Access changes
See Who Changed What
Access changes, in Admin's sidebar, lists every change to who is on the team and what they can do, each line naming who made it and tagged with its kind.
| Kind | What it lists |
|---|---|
| People | The team created, invitations sent and canceled, people joining (with who invited them) and removed, and ownership handed over |
| Roles | Roles changed, access given or taken away by name, and switches turned on or off for a role |
| Projects | Projects created, and people added to a project, removed from it or given another project role |
| Rules | The order approval amount, workspaces turned on or off, the Trash setting, two-factor sign-in required or no longer required, and anything the Owner removed from Trash under Keep all, with their reason |
| Plan | Plan changes, and complimentary seats or compute credits Conspecta adds |
Press Filter above the list and pick a kind to see only those changes.
The Owner sees every change, and so does anyone who can invite people, except that project changes are listed only to the Owner and Admins, who open every project. Everyone else sees the changes to their own role and access, and Export CSV downloads only those.
A person's page lists every project in the team in its Projects card, with what they can do on each and why. It reads Added as a project role, or From the Owner or Admin role. A project they can't open reads No access.
Export CSV, beside Filter, downloads every change the list holds for the kind you picked, one row each with when it happened, its kind, who made it, whose access it was and what changed, for an access review.
A person's page has its own Access changes card covering only them. You can always read your own.
Remove Someone From the Team
On a person's page, the Owner has Remove from and the team's name. Confirming takes away their access to every project in the team and everything given to them by name. Items they kept private in those projects pass to each project's lead and stay private. If you invite them back later, they start with nothing by name.
The Owner and Admins can also remove people from the team's page. See Removing members.