Skip to main content

Understanding roles and permissions

A plain-English breakdown of the four roles in Visibuild, what each one can and can't do, and how to change someone's role on a project or company.

Written by Louis Grist

By the end of this article you'll understand the four roles in Visibuild, what each one can and can't do, and how to change someone's role when needed.


The four roles

Company Admin is the top-level role. A Company Admin can invite people to the company, build company-wide templates, manage every project the company is on, and access the Company Dashboard for an executive view across all live projects. Typically held by QA Managers, Construction Managers, or office-based coordinators.

Project Admin is the senior role on a single project. A Project Admin can build the location tree, publish project templates, invite users and other companies to the project, and configure defect rounds. Typically held by the QA Lead or Project Manager on a project.

Partner Admin (Admin Limited) is the senior role for a partner company on a project, such as a subcontractor's lead. A Partner Admin can manage their own company's people on the project, build and publish their company's templates (subject to the head contractor's Template Review Mandate if enabled), and archive Visis their company created. They cannot edit the location tree or invite other companies. Every subcontractor on a project should have at least one person with this role.

Project Member is the general access role. Project Members can complete inspections and tasks assigned to them or their company, log issues, take photos, and use the mobile app. Most field users sit here. Project Members cannot perform admin functions.


What each role cannot do

Project Member: Edit the location tree, invite users or companies, configure defect rounds, archive Visis from other companies, access the Company Dashboard.

Partner Admin: Edit the location tree, invite other companies to the project, configure project-wide settings, archive Visis other companies created.

Project Admin: Change company-level settings. That's the Company Admin's job.

Company Admin: Company Admin alone does not automatically grant Project Admin rights on every project. Project Admins can be granted Company Admin rights separately.


How to change someone's role

The right person to make the change depends on which role you're assigning:

  • Company Admin: another Company Admin in your company can grant this.

  • Project Admin or Partner Admin: any Admin on that project can grant this.

  • If you're a Partner and nobody from your company has Partner Admin rights: ask the head contractor's Project Admin. They control project-level permissions.


What's next

To add users and companies to a project, see How to add companies and users to your project. To manage your company's members across all projects, see How to manage your team members and their access.

Did this answer your question?