š Overview
Not everyone on your team should see everything. Your field crew needs the schedule and daily logs, not your profit margins. Your bookkeeper needs invoices, not the bid you're about to submit. And a new hire probably shouldn't be able to delete a project on their first day.
Roles and Permissions let you decide what each role can do in Structur. In Settings > Permissions you pick a role and set an access level for every feature: Access Denied, View Only, Collaborate or Full Access. Everyone with that role gets the same access. You give each person their role in Settings > Users.
Access is set feature by feature, not as one level for the whole app. A project manager might have Full Access on Schedules and Tasks, Collaborate on Estimates, and Access Denied on Human Resources.
š Understanding Roles and Permissions
ā” What It Does
Settings > Permissions allows you to:
Pick a role and see its access level on every feature
Set one of four access levels per feature -- Access Denied, View Only, Collaborate or Full Access
Read what each level means for that feature in the Description column
Set a whole section at once with Set All Permissions
Create your own roles, starting from scratch or copying an existing role
Rename or delete roles, except the locked Owner and Company Admin
Search for a feature by name
See Recent Activity -- a log of permission changes
š When to Use It
Roles and Permissions are most valuable when you need to:
Keep financial details away from field and sales roles
Give a new kind of team member, like a site supervisor, a role that fits their job
Let someone view a module without being able to change or delete anything
Work out why a teammate can't see or edit something
š Step-by-Step Instructions
1. Open Permissions and Pick a Role
Click Settings in the left sidebar
Click Permissions
Click the role selector at the top left and choose the role you want to check
The tab opens on your own role. If you're the owner, it opens on Owner. A short description of the role shows under the selector.
The table has three columns: Feature, Description and Access. Features are grouped into sections, such as Preconstruction, Project Management and Financial Management.
Note: Always pick the role first. It's easy to read the wrong role's column and think a teammate has access they don't.
2. Understand the Default Roles
A new workspace has ten roles: Bookkeeper, Company Admin, Estimator, Field Crew, Foreman, Office Manager, Owner, Project Manager, Sales and Superintendent.
Owner -- the account owner. The Owner's access is fixed and can't be changed.
Company Admin -- "Manages the workspace, users, and settings across every area." It starts with Full Access on every row.
Owner and Company Admin can't be renamed or deleted. In a new workspace, roles such as Field Crew, Project Manager and Office Manager start at View Only on most rows, including the Settings rows.
The exceptions are Payments, Purchase Orders and Lien Waivers. They start at Access Denied for every role except Owner and Company Admin, so give access to the roles that need them. Field Crew also starts at Access Denied on Budget Margins.
3. Change an Access Level
Pick the role in the role selector
Find the feature, or type in Search permissions...
Click the access badge in the Access column
Choose the new level
The four levels:
Access Denied -- "No access to this feature."
View Only -- "Can view but not make changes."
Collaborate -- "Can create and edit, but not delete or manage settings."
Full Access -- "Full control, including delete and settings."
The Description column changes with the level and tells you exactly what it allows for that feature. For example, View Only on Takeoff reads "The user can view takeoff packages and sheets but cannot create, edit, or upload."
The change saves straight away, and you see "Permission updated successfully". There's no Save button.
Note: Changes apply to everyone with that role, not just one person.
4. Set a Whole Section at Once
Click Set All Permissions on the section's header
Under SET ALL FEATURES TO, choose Access Denied, View Only, Collaborate or Full Access
Every feature in that section moves to the level you choose straight away, with no confirmation, and you see "Permissions updated successfully". Use this to lock a role out of a whole area, such as Financial Management, in one step.
5. Create a New Role
Click + New Role
Enter a Role name (required), for example "Site Supervisor"
Under Copy permissions from, choose an existing role to start from, or leave it on Start from scratch
Add a Description of what the role can do
Click Create Role
You see "Role created". To work on the new role, pick it in the role selector. Then adjust its levels, and assign it to people in Settings > Users.
Each role needs its own name. If another role already uses the name, even with different capitals, a message says a role with that name "already exists on this team". Owner and Company Admin are reserved, and the message says the name "is a reserved role name and cannot be used". The window stays open, so change the name and click Create Role again.
A role started from scratch is View Only on most rows, and Access Denied on Payments, Purchase Orders, Lien Waivers and Budget Margins. Give it access to those rows if the job needs them.
6. Rename or Delete a Role
Open the role selector. Each role you can change has a pencil icon to rename it and a bin icon to delete it. Owner and Company Admin have no icons, because they're locked.
Rename: click the pencil. In Update Role, change the Role name or Description and click Save Changes. You see "Role updated successfully". The reserved names Owner and Company Admin can't be used here either.
Delete: click the bin. Structur asks if you're sure and warns "This action cannot be undone." Click Delete to confirm. You see "Role deleted successfully".
Note: Before you delete a role, move everyone who has it to another role in Settings > Users, so nobody is left without the access they need.
7. Check Who Sees Leads and Projects
The Leads Pipeline row (under Preconstruction) and the Projects Pipeline row (under Project Management) are separate. A role can have one level on leads and a different level on projects.
These rows also decide which leads and projects a person sees. With Full Access, a role sees every lead or project. With View Only or Collaborate, people see the leads and projects they're assigned to in Manage Members on the record's Overview, for example as a Sales Rep or Project Manager.
People with the Field Crew or Foreman role are the exception: with View Only or Collaborate, they see every lead or project without being assigned.
If a teammate can't find a job, check their role's level on these two rows, then check that someone has added them to the record in Manage Members on its Overview.
8. Review Recent Activity
Below the table, Recent Activity lists permission changes, newest first. Each entry shows who made the change, the feature and role, the old and new level (for example "Access Denied ā View Only") and when. Creating, renaming and deleting roles, and Set All Permissions changes, show here too. In a new workspace it reads "No permission changes yet."
šļø Permission Rows by Section
Structur AI: Structur AI
Preconstruction: Leads Pipeline, Embed Form, Overview, General, Intake, Ballparks, Takeoff, Estimates, Proposals, Bid Packages
Project Management: Projects Pipeline, Tasks, Daily Logs, Schedules, Timesheets, Submittals, Checklists, RFI's, Files, Punchlists, Emails, Meetings, Selections
Financial Management: Allowances, Budget, Budget Margins, Subcontracts, Purchase Orders, Payments, Lien Waivers, Expenses, Change Orders, Invoices, Receipts
Task Boards: Task Boards
Company Operations: Org Chart, Employee Handbook, Standard Operating Procedures, Human Resources, Admin
Systems Accelerator: Video Training, Templates, Resources, My Program
Settings: Company, Users, Groups, Permissions, Clients, Vendors, Cost Codes, Billing, Integrations, Affiliate Area
Punchlists, Meetings and Selections are marked Coming soon, for features that are still on the way. Purchase Orders and Lien Waivers are normal rows that you can set like any other.
Budget Margins controls who sees your internal margins: "The user can see internal margins on the Budget, including the Include margins toggle and the Internal Markup column." It's separate from the Budget row, so a role can see the Budget without seeing your margins.
ā Best Practices
Pick the role before you read the table -- the tab opens on your own role, so it's easy to check the wrong column.
Review the defaults in a new workspace -- most default roles start at View Only on most rows, including Settings, and at Access Denied on Payments, Purchase Orders and Lien Waivers, which may be more or less than you want.
Copy an existing role instead of starting from scratch -- Copy permissions from gives you a sensible base, so you only change what's different.
Use Set All Permissions to lock out whole areas -- setting Financial Management to Access Denied in one step is faster and safer than row by row.
Read the Description before you choose a level -- it says exactly what that level allows for the feature.
Set Tasks and Task Boards together -- they're separate rows, so access to one doesn't give access to the other.
Name custom roles after the job -- "Site Supervisor" tells the next admin far more than "Role 2".
ā Common Questions
Q: What's the difference between Full Access and Collaborate?
A: Collaborate can create and edit, but not delete or manage settings. Full Access has full control, including delete and settings. On the Leads Pipeline and Projects Pipeline rows, Full Access also sees every lead or project, while Collaborate sees the ones the person is assigned to.
Q: My teammate has the right access but still can't do something. Why?
A: First, pick their role in the role selector and check the row again. The tab opens on your own role, not theirs. Then check the related rows. For example, Tasks and Task Boards are separate rows. If it still looks right, ask them to refresh or sign out and back in.
Q: Can I give one person more than one role?
A: No. Each user has one role. If someone needs a mix, create a new role with + New Role, copy permissions from the closest existing role, adjust it, and assign it to them in Settings > Users.
Q: Can I change one person's access without changing everyone in their role?
A: Not directly. Access is set per role. Create a new role for that person, set its levels, and assign it to them in Settings > Users.
Q: What's the difference between Owner and Company Admin?
A: Owner is the account owner, and its access can't be changed. Company Admin starts with Full Access everywhere and "Manages the workspace, users, and settings across every area." Neither role can be renamed or deleted. To make someone else the owner, see Company Settings.
Q: My project manager can't see any projects. Do I add them to each one?
A: If their role has View Only or Collaborate on Projects Pipeline, yes. They see the projects they're assigned to in Manage Members on the project's Overview. To let a role see every project, give it Full Access on the Projects Pipeline row.
Q: How do I hide our margins from some roles?
A: Set the Budget Margins row for that role. It controls the Include margins toggle and the Internal Markup column on the Budget. The Budget row on its own doesn't decide this, so check both.
Q: My bookkeeper can't see Payments. Why?
A: Payments, Purchase Orders and Lien Waivers start at Access Denied for every role except Owner and Company Admin. Pick the role in Settings > Permissions and set those rows to the level the job needs.
Q: Do Groups control permissions?
A: No. Groups are for team messaging only. Access comes from each person's role. See Groups.
ā ļø Common Mistakes to Avoid
ā Don't | ā Do |
Read the table without picking the role first | Choose the teammate's role in the selector, then check the row |
Give everyone Full Access to avoid questions | Give each role only the access its job needs |
Change a default role for one person | Create a custom role for them instead |
Set Tasks and forget Task Boards | Set both rows, because they're separate |
Delete a role people still have | Move them to another role in Settings > Users first |
Expect View Only or Collaborate users to see every project | Add them in Manage Members on the record's Overview, or give Full Access on the pipeline row |
