users

User Access

User Access gives admin users granular control over exactly what each non-admin user can see and interact with — which infrastructure projects, deployment projects, cloud accounts, and other resources they have permission to access.

What is User Access?

Assigning a role to a user in the User List defines their global capability level — what actions they are permitted to perform. User Access goes one level deeper and controls which specific resources they can see and act on. A user with the Editor role but no project access cannot see any projects. A user with access to only the dev cloud account cannot interact with production resources.

This two-layer model — role plus access — gives your organisation precise control over your team's reach within QuickInfra. It is especially important in production environments where only certain people should be able to trigger infrastructure changes or deployments.

What You Can Control

Infrastructure Projects — Which infrastructure projects a user can view and interact with. A user without access to a project cannot see it in their Projects list at all.
Deployment Projects — Which deployment projects a user can access and execute. Useful for restricting production deployments to senior team members only.
Cloud Accounts — Which connected cloud accounts a user can see and use when fetching resources or executing projects. Users without access to the production cloud account cannot query or deploy into it.
Other Resources — Access to specific sections such as VM Instances, Disk Volumes, Networks, and other Manage features can be scoped per user based on your organisation's requirements.

Note:Admin users always have full access to everything regardless of User Access settings. Access controls only apply to Editor, Developer, and Viewer roles.

Tip:A common pattern is to give Developers access to dev and staging infrastructure projects and deployment projects, while restricting production access to Editors or senior team members only. This prevents accidental production changes while keeping the team productive.

Key Things to Know

User Access is additive — a user only sees resources explicitly granted to them. Nothing is visible by default for non-admin users until access is assigned.
Access changes take effect immediately — the user does not need to log out and back in.
Removing access to a project or resource removes it from the user's view instantly — any active session will no longer show the resource on next navigation.
User Access works alongside roles — a user must have both the appropriate role capability and explicit resource access to perform an action.