Skip to main content

How access works

The whole platform uses one rule:

Everything you make is yours. You can share it with a team or with the whole organization. Someone who approves for that team or the organization says yes.

The rule is the same for checklists, workflows, code books and team files. Learn it once.

1. Everything starts private​

When you make something, only you can see it. That covers a new checklist, a saved workflow, a code book you upload, or a file in Documents on My Dashboard.

This is on purpose. You can work on something half-finished without anyone else seeing it.

2. Teams and your organization​

There are two places you can share with.

  • Your organization is everyone at your firm. Its page is Organization, under TEAMS in the sidebar.
  • A team is a smaller group inside your firm. It can be an office, a discipline, a client, or a region. Each team has its own team page.

Your firm picks its own teams. An org owner makes them. A team lead can add sub-teams under a team they lead.

You can be in more than one team. That is why sharing has three steps, not two: only you, a team, or everyone.

Who can open a team​

By default, only a team's members can open its page and see what is shared with it. The team's settings can open it wider. Look for Who can see this on the team in the tree:

  • Same as the team above it
  • Only members of this team
  • Everyone in the team above it
  • Everyone in the organization

Everyone in the organization can always see a team's name, its lead, and its counts. The members list, the items and the projects show only to people the team lets in.

When a team is deleted​

An org owner can delete a team. Its page still opens and says "This team has been deleted."

  • You can't share anything new into it.
  • What was already shared with it still works for the people who were members. It can still be taken back.

Deleting a team does not take access away. To take access away, take the items back.

3. Sharing is a request, not a switch​

Sharing is usually a request. You ask, and someone else says yes.

Only me → Shared with a team → Shared with organization

How to share a checklist with the organization​

  1. Open My Dashboard in the sidebar, then the Documents tab.
  2. Find a checklist you own and press Ask to share.
  3. A panel called Who can use this opens. It shows who can use the checklist now.
  4. Under Share with, press Share next to Everyone in the organization. To share with one team instead, press Share next to that team.
  5. The row now says Sent for review.

The people who can approve get an email and a notification. The request also shows in their Requests.

Nothing changes until they approve. If they decline, you are told why. Fix it and press Re-request. You lose nothing.

You can see three kinds of things: your own, anything shared with the whole organization, and anything shared with a team you are in (or a team above yours).

Who approves what​

Sharing withWho approves
A teamThat team's leads, leads of any team above it, and org owners
The whole organizationOrg owners and any team lead, unless your organization lets only org owners approve

An org owner picks one of these in Organization → Settings → Who can approve organization-wide sharing.

Code books are a little different. They reach the whole organization through the code library's publish step. An org owner approves it. Once a code book is shared with the whole organization, any team lead can rename it (the name only, not its other details), unless your organization lets only org owners approve. See Code Review.

If you are the approver​

If you already approve for a team, your own share into that team goes live at once. Nobody is asked, because you would be asking yourself. The same is true for the organization if you are one of its approvers.

A team lead can also share checklists, workflows, Revit workflows and code books that belong to their team, even if a member made them.

Working your queue​

If you approve things, requests come to you in three places:

  • Requests in the sidebar lists everything waiting on you. See Requests & My issues.
  • A team's page shows its own requests, with a note saying how many and which tab.
  • The Organization page shows organization requests at the top.

Each request opens a panel with Approve, Decline…, the item's details, and a conversation.

Declining is a conversation, not a dead end​

You must give a reason to decline. The requester reads it.

The reason starts a conversation on the request. The requester can reply. A reply opens the request again, so they don't have to start over.

4. What the rule covers​

ThingWhere it lives
ChecklistsChecklists & custom checks
WorkflowsWorkflows
Revit workflowsConnect Revit
Team filesTeams and My Dashboard
Code booksCode Review

5. Roles​

A role says what you are allowed to do. That is a different question from who can see something.

In the organization​

RoleWhat it means
ViewerRead-only. Can open projects, drawings and findings they have access to, and ask questions in chat. Can't upload, run checks, change findings, or edit anything.
MemberThe normal role. Works on projects, runs checks, and uploads. Their uploads stay private until they ask to share.
OwnerRuns the organization. Invites people, changes roles, and makes teams. Also looks after the code library: approves or declines code books shared with the whole organization.

A viewer is read-only everywhere in Structured, including the add-ins. A viewer can sign in to the Revit, AutoCAD or Archicad add-in, connect it to a project, read findings and chat. They can't send to the project, upload or run checks from an add-in. In Revit and AutoCAD the assistant can read the open model for them but is set up not to change it. A viewer who tries to change something sees "Your access is view-only".

An org owner can also make a member read-only in the add-ins while they keep full member access in the web app. On the Settings tab of the Organization page, open Permissions and find Who can change the model from the CAD add-ins under Integrations. Members and team leads are ticked by default, so nothing changes until you untick them; you can tick a custom role to let only some people change the model. Someone who is not ticked can still sign in to the add-ins, read findings and chat there, but can't send to the project, upload or run checks from an add-in, and in Revit and AutoCAD the assistant only reads the open model. Panels that open the web app inside an add-in, such as Clash Review, keep the person's web access. Org owners can always change the model from the add-ins, and viewers never can.

Who can see the organization's full member list, with everyone's name, email and role, is also a setting. On the same Permissions page, find Who can see the full member list under Members. Members and team leads are ticked by default. Someone who is not ticked, and every viewer, sees only the organization's owners, so they still know who to ask for access. On a project shared with the whole organization, they see the people added to the project, the person who created it, anyone a shared team brings in, and the owners, rather than everyone in the organization. Org owners can always see the full list.

Lead is not an organization role. It is a flag on one team. A lead approves what is shared with their team, and can edit their team and every team under it. An org owner makes someone a lead.

Only an org owner (or an admin) can add a team at the top of the tree.

Someone outside your firm can be invited to one project as an external collaborator. They only see what they are given.

On a project​

Projects work differently. A project is shared with named people, not with a team. Each person gets a role on that project:

RoleCan
OwnerEverything, including sharing and deleting the project
EditorRun checks, upload, comment, mark up, and work on issues
ViewerRead the drawings, findings and outputs, but not change them

Open a project and press Share. You can also share a project with the whole organization.

An org owner can make every new project start shared with everyone, as Can view or Can edit. This is in Organization → Settings → New projects. It only affects new projects.

6. Who can see private things​

There are two things to know:

  • Org owners can see every checklist, workflow and Revit workflow in the organization, including private drafts. They see them on the Organization page's Inventory tab. This lets an owner help when someone leaves in the middle of a job.
  • Team leads can't see members' drafts. A lead only sees what is offered to their team.

Other pages​