Roles & Permissions

vlx provides two layers of user access control organization level roles and team level roles this structure ensures you can manage access to templates, inspections, and projects across your company while maintaining flexibility within each operational team organization roles organization roles organization roles define what a user can manage at the account level these permissions apply across all teams and control access to users, teams, settings, and billing while owners, super admins, and admins have organization wide authority, members have no global permissions by default—their access is defined entirely by the role they are assigned within each team owner the owner is the user who originally created the organization this role has full control over the account, including billing, subscription management, user and team management, and all data across the organization only the owner can delete the organization ownership can be transferred to another user if needed super admin full administrative access without the ability to delete the organization super admins can manage users, teams, settings, inspections, projects, templates, and billing admin operational control across the organization admins can manage users, teams, and all content, but do not have access to billing or subscription management member the base organization role members have no organization wide permissions what they can see and do is determined entirely by the role they are assigned within each team organization role permissions overview permission area owner super admin admin member (team level) manage organization details & branding ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✖︎ ✖︎ delete organization ✔︎ ✔︎ ✖︎ ✖︎ ✖︎ ✖︎ ✖︎ ✖︎ add/remove users, manage roles ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✖︎ ✖︎ billing & subscription management ✔︎ ✔︎ ✔︎ ✔︎ ✖︎ ✖︎ ✖︎ ✖︎ create teams ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✖︎ ✖︎ view all teams ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✖︎ ✖︎ delete teams ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✖︎ ✖︎ change team settings ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ team role view inspections/projects/templates ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ team role edit inspections/projects/templates ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ team role create inspections/projects/templates ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ ✔︎ team role legend ✔︎ ✔︎ = allowed ✖︎ ✖︎ = not allowed team role = determined by the user’s role within each team note the organization role defines global permissions but does not automatically grant access to inspections, templates, or reports that’s controlled at the team level team roles team roles team roles provide a granular access control and define what a user can see and do within a specific team admin full control of the team manage team members and roles manage team settings create, view, and edit all projects and inspections contributor contributors can create and update projects and inspections based on their access level full access edit all inspections and projects view all inspections and projects use for team leads and managers who need full team operational access limited access edit own / assigned inspections view all inspections and projects use for contributors who work on their own items but need visibility into the team’s work focused access edit own / assigned inspections view own / assigned inspections use for field users and collaborators who should only see their own work viewer view only access can view inspections and reports shared with the team cannot create, edit, or submit inspections no access to projects, templates, or team settings 🔁 users can have different roles in different teams for example, someone could be an admin in the "cleaning crew" team and just a viewer in the "maintenance" team how to invite and assign roles how to invite and assign roles invite to the organization go to the users tab in the sidebar click invite user enter their email and assign their org level role (super admin, admin, or member) click send invitation add to a team go to the teams tab select the team you want click add user enter their email and assign a team specific role choose what level of access you want them to have within that team quick example you want your regional manager to oversee multiple teams, but only give field inspectors access to their own work assign the manager an admin org role and make them a team admin in all relevant teams assign field inspectors the member org role and then make them contributor (limited) in their assigned team