Vicket Documentation

Organizations and Access

Last updated February 28, 2026

Roles, permissions, and access boundaries across organizations and teams.

Organization membership roles

Vicket supports organization-level roles:

  • owner
  • admin
  • member

Permission model highlights

  • Organization settings and billing actions are owner-only
  • Invitations can be managed by owner and admin
  • Workflow management requires owner/admin and eligible plan
  • Website create/update is owner/admin, website delete is owner-only

Team-level permissions

Teams have their own member roles:

  • admin
  • member

Team admins (plus organization admin/owner) can manage team configuration.

Access behavior for ticket visibility

Ticket access is based on role and routing:

  • Organization owner/admin can access all org tickets
  • Team members access tickets assigned to their teams
  • For unassigned tickets, template visibility rules apply

Organization lifecycle

  • You can switch active organization from the dashboard
  • Organization deletion is a protected owner action
  • On creation, each organization is pre-populated with example content (a template, a FAQ, and an article) to help you get started quickly

Use separate organizations for strict tenant boundaries.

Inviting members

Organization owners and admins can invite new members by email. Navigate to Settings > Members and enter the recipient's email address. The invitee receives a link to join the organization. If they do not yet have a Vicket account, the invitation flow guides them through registration first.

Pending invitations are visible in the members list and can be revoked before acceptance. Each invitation is tied to a specific role that the new member will receive upon joining.

Managing member roles

Once a member has joined, owners can promote or demote them between the member, admin, and owner roles. Admins can promote members to admin but cannot assign the owner role. Role changes take effect immediately and update the member's permissions across all websites and teams within the organization.

To remove a member entirely, owners and admins can revoke their membership from the members list. Removed members lose access to all organization data, including tickets they were previously assigned to.

Multi-organization support

A single Vicket account can belong to multiple organizations. Use the organization switcher in the dashboard sidebar to move between them. Each organization maintains fully isolated data, billing, and member lists. This is particularly useful for consultants or agencies that manage support operations for several clients from one account.

Organizations and billing

Billing is scoped per organization. Each organization holds its own subscription and plan, managed by the owner. Plan limits such as storage quota, workflow count, and website count apply independently to each organization. See Billing and Plans for details on available tiers and usage tracking.

Best practices for agency setups

If you operate an agency managing support for multiple clients, consider these patterns:

  • Create one organization per client to enforce strict data isolation
  • Use the owner role sparingly — assign it only to agency principals who need billing access
  • Add client stakeholders as member or admin depending on whether they need configuration access
  • Pair each website with a dedicated team so agents only see relevant tickets
  • Review member lists periodically to revoke access for staff who have rotated off a project

On this page