Skip to content

Give a user access to a site

Owners and Administrators see every hosting. Operators, Read-only users and users on an Only assigned custom role see only the hostings an Owner grants them. You grant and revoke access on each hosting’s Access tab.

  • Sign in as an Owner. The Access tab is not shown to anyone else.
  • The user exists and has a role that works per site. See Add and manage panel users.
  • Know which level you want.
    • Manage (full CRUD): the user can change the hosting, limited by what their role allows.
    • Read (view only): the user can view the hosting. Any action that changes it is refused with a 403 page.
  1. Open Hostings in the sidebar and click the site.
  2. Click the Access tab, under Admin in the tab list. Its heading is Access and the card is Per-user access.
  3. In User, pick the account. Each entry reads <username> (<role>).
  4. In Level, choose Manage (full CRUD) or Read (view only).
  5. Click Grant access.

To change a level, grant again for the same user with the other level. The grant is replaced. To remove access, click Revoke on the user’s row and confirm Revoke. The dialog reads “This user will no longer be able to see or manage” followed by the domain.

  • The Access tab lists the user with a manage or read pill and the time it was granted. The tab label shows the number of grants.
  • Ask the user to open Hostings. The site is in their list. Before the grant it was not.
  • A grant needs the role’s capability as well. A user at manage level still cannot, for example, delete a site unless their role includes Delete hostings. See Built-in roles and capabilities.

Moving or copying a site with Move / copy carries its access grants to the new site. The transfer log says “access grants carried over” followed by the count.

  • The Access tab is missing: you are not signed in as an Owner.
  • The user is not in the User list: their role is not Operator or Read-only. Change the role on Users. If the person should see every site, assign the Administrator role or a custom role with All hostings scope instead.
  • The user gets “403 Forbidden”: they have no grant on that site, or a read grant and the action changes something. Grant Manage (full CRUD) and check their role includes the capability.