Share Links and Access

Each role link grants only that role's permissions. Choose between persistent membership for a signed-in person and direct access for anyone holding an anonymous link.

With Allow anonymous turned off, the visitor must sign in. Opening the link adds that account as a member of the role and redirects to the normal server page in their Console. The shared server is marked Shared.

Membership continues after the original link is revoked. To end access, someone with Manage sharing must remove the member or delete the custom role. A member can also leave the shared server from their Console, which removes all of their memberships on that server.

Use login-required access when you want to see and manage individual members over time.

With Allow anonymous enabled, the visitor does not need to sign in and is not added to the Members list. Anyone with the complete link can use the role's allowed controls.

Use anonymous access only for permissions appropriate for every person who might receive the URL. Revoke the link immediately if it reaches an unintended audience. Because anonymous access does not create membership, revoking the link ends access through that URL.

Permissions still apply

Neither link type grants more than the selected role. A visitor can view or use only the sections covered by that role's permissions. If the same signed-in user belongs to several roles, those role permissions are combined on the normal Console page.

Billing always stays with the owner

Starting, resizing, and running the server always use the owner's credits. A shared visitor is not charged from their own balance. If the owner lacks enough credits, a shared user's start or more expensive configuration change does not proceed.