Skip to main content

2-Tier Permissions

How Structur decides who sees each lead and project: first the role's level on the Leads Pipeline or Projects Pipeline row, then whether the person is assigned in Manage Members on the record's Overview.

Written by Support

šŸ“‹ Overview

Not everyone on your team needs to see every job. Your estimator needs the leads they're pricing, your superintendent needs the projects they're running, and you need to see all of it.

Structur decides who sees each lead and project in two steps, or "tiers". First it checks the person's role in Settings > Permissions. If the role doesn't give full visibility, it then checks whether the person is assigned to that lead or project in Manage Members.

Once you know the two tiers, most "I can't see this job" questions take a minute to fix.


šŸ” Understanding 2-Tier Permissions

⚔ What It Does

The two tiers work like this:

  • Tier 1, the role -- the role's level on the Leads Pipeline row (for leads) or the Projects Pipeline row (for projects)

  • Tier 2, the assignment -- for View Only and Collaborate, whether the person is assigned to that lead or project in Manage Members

  • Same rule everywhere -- it decides which leads and projects show in the pipeline, and who gets notifications about them

šŸ“… When to Use It

Understanding the two tiers is most valuable when you need to:

  • Keep certain jobs private from people who aren't working on them

  • Let estimators and project managers see only the jobs they're on

  • Let owners and senior staff see everything without adding them to each job

  • Work out why a teammate can't find a lead or project


šŸ“ Step-by-Step Instructions

1. Tier 1: The Role's Level

Structur first looks at the person's role in Settings > Permissions:

  • Access Denied -- the person doesn't see leads (or projects) at all, even if they're assigned to one

  • Full Access -- the person sees every lead (or project). No assignment is needed

  • View Only -- the person can view, but not create, edit or delete. Go to Tier 2

  • Collaborate -- the person can create and update leads (or projects) and take part in workflows, but can't manage settings. Go to Tier 2

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.


2. Tier 2: The Assignment

Tier 2 only applies to View Only and Collaborate. The person sees a lead or project only if they're assigned to it in Manage Members, in any of these:

  1. Sales Rep(s)

  2. Estimator(s)

  3. Project Manager(s)

  4. Superintendent(s)

  5. Additional Member(s)

If they aren't in any of them on that record, they don't see it.

People are also added to Additional Member(s) automatically when someone assigns them a task or schedule item on the project, or when they log their first time entry on it.

Note: The Vendors section in Manage Members is for vendors, not your team. It doesn't give anyone access.

Note: People with the Field Crew or Foreman role skip Tier 2. With View Only or Collaborate, they see every lead or project without being assigned.


3. Set a Role's Level

  1. Click Settings in the left sidebar, then Permissions

  2. Choose the role in the role selector at the top left

  3. Find Leads Pipeline or Projects Pipeline, or type in Search permissions...

  4. Click the access badge in the Access column and choose Access Denied, View Only, Collaborate or Full Access

The change saves straight away and you see "Permission updated successfully". There's no Save button. It applies to everyone with that role.


4. Assign Someone to a Lead or Project

This is only needed for roles with View Only or Collaborate on the pipeline row.

  1. Open the lead or project

  2. On Overview, click Edit in Project Details

  3. Click Manage Members

  4. Under Sales Rep(s), Estimator(s), Project Manager(s), Superintendent(s) or Additional Member(s), search for the person and add them

  5. Click Save Changes

Everyone assigned shows in the Project Directory table on the record.


5. Fix "I Can't See This Job"

  1. In Settings > Permissions, choose the person's role and check Leads Pipeline (for a lead) or Projects Pipeline (for a project)

  2. If it's Access Denied, that's the reason. Change the level if they should see it

  3. If it's View Only or Collaborate, open the lead or project and check Manage Members on its Overview

  4. If they aren't listed, add them and click Save Changes


⭐ Best Practices

  • Give View Only or Collaborate to most roles -- keep Full Access for owners and senior staff who need to see every job.

  • Assign the team when the job starts -- set Sales Rep(s), Estimator(s), Project Manager(s) and Superintendent(s) as soon as you know them.

  • Use Additional Member(s) for everyone else -- anyone who needs the job but doesn't fit the other roles.

  • Use Access Denied on purpose -- for roles that have no reason to see leads or projects at all.

  • Check both rows -- leads and projects are set separately, so a role can see one and not the other.

  • Don't add Full Access users to every job -- they already see everything.


ā“ Common Questions

Q: A user has View Only but still can't see a project. Why?

A: View Only means Tier 2 applies. Open the project, click Edit in Project Details on its Overview, then Manage Members, and add them under one of the five people sections.


Q: Do I need to add Full Access users to every project?

A: No. Full Access on the pipeline row sees every lead or project automatically.


Q: Will someone get notifications about a job they can't see?

A: No. Structur uses the same two tiers to decide who gets notifications about a lead or project.


Q: What's the difference between View Only and Collaborate here?

A: Both use the same Tier 2 check to decide which leads and projects someone sees. The difference is what they can do once they're in: View Only can only look, while Collaborate can create and update.


Q: Can two people with the same role have different access?

A: No. Levels are set per role, not per person. Create a separate role with + New Role and assign it in Settings > Users.


Q: Why did someone appear under Additional Member(s) on their own?

A: They were assigned a task or schedule item on the project, or logged their first time entry on it. That adds them automatically so they can see the project.


āš ļø Common Mistakes to Avoid

āŒ Don't

āœ… Do

Add a person under Vendors and expect them to see the job

Add them under Sales Rep(s), Estimator(s), Project Manager(s), Superintendent(s) or Additional Member(s)

Give everyone Full Access for convenience

Keep Full Access for owners and senior staff

Forget to assign the team when a job starts

Set Manage Members as soon as you know who's on the job

Assume View Only sees every project

Assign them in Manage Members, or give Full Access on the pipeline row

Set Projects Pipeline and forget Leads Pipeline

Check both rows, because they're separate

Check the wrong role's level

Choose the person's role in the selector first

Did this answer your question?