Skip to main content

Organization page

The Organization page is the whole firm on one page. Open it from Organization under TEAMS in the sidebar. Dashboard in your account menu also brings owners here, on the Overview tab. Your own page, with your memory, labels and settings, is My Dashboard.

It works like a team page: a line at the top that says where you stand, then tabs. But it covers everyone in the firm.

Tabs, by role​

What you see depends on your role:

TabMemberTeam leadOrg owner
Projects: every project in the organization--Yes
Checklists, Workflows, Revit workflows, Resources: what is shared with the whole organizationYesYesYes
Members: everyone in the organization--Yes
Teams: the tree and a table of every teamYesYesYes
Overview: how the checks are doing-Yes (teams you lead)Yes
Inventory: every checklist, workflow, Revit workflow and code book-Yes (teams you lead)Yes
Settings: the organization's settings--Yes

Workflows only shows if your organization has Workflows turned on. The page opens on Teams. Your own work is on My Dashboard.

Memory and Labels are not tabs here. Everyone, owners included, finds the organization's memory and labels on the Memory and Labels tabs of My Dashboard. See Memory and Labels.

Organization requests​

At the top of the page, owners and team leads see Organization requests. These are requests to share something with the whole organization. Each one opens a panel with Approve, Decline…, and a conversation. A decline needs a reason. See How access works.

  • Several people can answer. By default, org owners and any team lead can approve. An owner can limit this to owners in Settings.
  • Team requests go elsewhere. They go to that team's leads, on the team's page.
  • Everything is also in Requests, in the sidebar.

Recent decisions lists what was already approved or declined.

Overview​

Ask a question​

Overview starts with an Ask box. Type a question in plain words, or start from an example. The answer shows as a chart underneath. Your past questions are listed beside it.

For example: "How many issues did each discipline have last quarter?"

For an org owner, it answers about the whole organization.

The cards​

  • Check quality: issues found per check run, how many were marked "not an issue", issues found against issues resolved, and the mix of severities.
  • Recurring issues: the issue types that keep coming back, with how often. If the same mistake shows up on many jobs, it is likely a standards or template problem.
  • Quality over time: issues found per 100 sheets, week by week.
  • Tool usage: how many people used the platform, which features they used, and who has Gone quiet.

An Organization summary says it in plain sentences: what is going well, what needs attention, and which checks to change or drop.

Narrowing it​

  • Team narrows every card to one team or sub-team. "Unassigned" shows projects that are in no team yet. A team lead only sees the teams they lead.
  • The period buttons (4 weeks, 13 weeks, 52 weeks, or Custom) set the time window for Overview and Inventory.
  • Generate leadership report prints the Overview as a clean report.

A project in two teams counts in both. That way a team's numbers and the organization's numbers agree.

Teams​

This tab shows the tree: the organization at the top, then every team and sub-team under it. Below the tree, a table lists every team, who can see it, and its counts. Everyone can see this tab. Teams you can't open show as locked.

Org owners set things up here. They add teams and sub-teams and set Who can see this for each. The organization's labels are on the Labels tab of My Dashboard (see Labels).

Inventory​

A list of every checklist, workflow, Revit workflow and code book in the organization. It shows the owner, which teams it is shared with, and when it last ran. Owners see everything, including private drafts. A team lead sees only what belongs to the teams they lead, and never someone else's private items.

Members​

The list of everyone in the organization, for org owners: roles, teams, leads, labels, invites, and changes to many people at once. See Organization members & invites.

Settings​

For org owners. Each setting has its own Save:

  • New projects: Only the people added or Everyone in the organization, as Can view or Can edit. Only affects new projects.
  • Organization name.
  • Default language for new members. People already in keep their own language.
  • Require teams and labels: shown here, changed on the Labels tab of My Dashboard. See Labels.

Permissions​

Below the settings, Permissions sets who in your organization can do certain things. Org owners can always do all of them. Only org owners see this section. Each permission has its own Save; Default marks the standard choice, and once someone changes a permission it says who changed it last and when. The first choice listed for each is the default.

Sharing and usage

  • Who can approve organization-wide sharing: Org owners only or Org owners and team leads.
  • Who can open Usage & Billing: Org owners only or All members, if your organization has Usage & Billing.

Checklists

  • Who can edit custom checklists: The creator and team leads, Only the creator or Anyone who can see it. A team lead here is the lead of a team the checklist is shared with, or of a team above it.
  • Who can delete custom checklists: The creator and team leads or Only the creator.
  • Who can share custom checklists with teams: The creator and team leads or Only the creator.
  • Who can edit pre-built checklists (including hiding them): Org owners and team leads, Org owners only or Anyone who can see it.

Workflows

  • Who can edit workflows: The creator and team leads or Only the creator.
  • Who can delete workflows: Only the creator or The creator and team leads.
  • Who can share workflows with teams: The creator and team leads or Only the creator.

Resources

  • Who can share resources with teams: Only the person who added it or The person who added it and team leads.
  • Who can delete resources: The person who added it and team leads or Only the person who added it.

Code books

  • Who can approve code books for the organization: Org owners only or Org owners and team leads. Whoever can approve also sees every code book uploaded in the organization, including ones not shared yet.
  • Who can delete code books for everyone: Org owners, and team leads until it is shared or Org owners only. Anyone can still remove a book from their own codes.
  • Who can edit a code book's details: Uploaders and team leads, until it is shared or Uploaders only, until it is shared. Once a book is shared with the whole organization, only org owners can edit its details.

On the legacy layout, this is under Dashboard in the account menu. See The legacy layout.