Roles & permissions

Permissions that scale from one team to many clients

Separate workspaces, assign roles at workspace and project level, and keep sensitive data visible only to the right people.

  • Workspace roles
  • Project roles
  • Multi-tenant
Workspace boundarySeparate clients, departments, or brands cleanly
Project-level accessFine-grained roles inside each workspace
Invite external usersGive clients limited visibility without admin rights
Consistent everywherePermissions apply to views, imports, and automations

Why permissions

Control who sees what as you add teams and clients

Gzodo separates workspace administration from project collaboration — so sensitive data stays with the people who need it.

  • Workspace roles

    Manage members, billing, and workspace-wide settings.

  • Project roles

    Fine-grained access per project inside a workspace.

  • Multi-tenant ready

    Run client or department workspaces with clear boundaries.

How it works

Layer access from workspace down to project

  1. 01

    Create a workspace

    Each workspace is an isolated environment for a team or client.

  2. 02

    Assign workspace roles

    Owners manage billing and members. Members access projects they are invited to.

  3. 03

    Set project roles

    Control who can view, edit, or administer each project inside the workspace.

Use cases

Permissions that scale with your organization

  • Agencies

    Run one workspace per client with separate member lists.

  • Enterprise departments

    Give finance read-only access while ops stays in Editor.

  • External partners

    Invite vendors to a single project as Viewers.

  • Onboarding contractors

    Grant temporary Editor access without workspace admin.

Role overview

Workspace vs project access at a glance

RoleWorkspaceProject
ViewerRead projects and viewsView items only
EditorCollaborate across projectsEdit items and views
AdminManage members and billingFull project control

Access control

Roles that work across every Gzodo feature

  • Role templates for common team structures
  • Control views, edits, and administration separately
  • Works with forms, imports, and automations
  • Audit-friendly separation between workspaces
Editor
  • View and edit project items
  • Configure views and fields
  • Cannot manage workspace billing

FAQ

Common questions about roles

Can external clients have limited access?

Yes. Invite users to a workspace or project with roles that restrict what they can see and change.

What is the difference between workspace and project roles?

Workspace roles cover members, billing, and settings. Project roles control who can view or edit items inside a specific project.

Do permissions apply to imports and automations?

Yes. Access rules apply across views, imports, forms, and workflows — not only the item list.

Can I isolate one client from another?

Yes. Use separate workspaces so members, data, and billing stay bounded per client or department.

Ready to invite your team safely?

Create a workspace, assign roles, and invite members with the right level of access.