Thora Cloud
A direct line to Thora

Start a conversation

What can we help make simpler?

Tell us what you need. A real person will point you to the right place.

Email Thorahello@thora.cloudExplore SupportSee the available support paths
Browse docs Access and sign-in

Help and guides

Access and sign-in

Sign in to the right account and check your organization membership.

Before you start

Use your own Thora Cloud account. Organization membership determines which resources you can access.

Steps

  1. Sign in through the normal Thora Cloud sign-in screen.
  2. Select the organization you want to work in.
  3. If a private preview asks you to sign in again, follow its sign-in link.
  4. Ask an organization administrator to check your membership or role if you cannot access a resource.

What to expect

You can access the resources allowed by your current membership and role. Some changes require an administrator or a separate approval.

If something goes wrong

An expired session or removed membership can end access. Sign in again to refresh your session; do not send cookies, passwords, or tokens to another person to resolve an access problem.

Technical reference

Developer credentials

A developer credential belongs to one user and one organization. The full token is returned once; Thora stores only a digest and display prefix. Each request rechecks membership, activation, expiry, revocation, and scope.

  • Expiry is 1–90 days.
  • A user may have at most 10 active credentials per organization.
  • Only direct administrators can issue write credentials.
  • Removing membership, revoking the credential, or losing required administrator status blocks later requests.

Management scopes

Existing credentials do not automatically gain newly introduced scopes. Issue a replacement only when the user needs the new capability, then revoke credentials that are no longer required.

Current scope familiestext
management:profile:read
management:organization:read
management:resources:read
management:usage:read
management:compute:read
management:compute:write
management:ai:read
management:dns:read
management:dns:write
management:git:read
management:git:write
management:sites:read
management:sites:write

Remote MCP OAuth

For browser-capable remote MCP clients, use Thora Auth resource-bound OAuth with PKCE and consent. New account connections discover current organizations without an initial organization picker; existing grants retain their original organization. Validate issuer, audience, time claims and scopes. A generic Thora identity token is not an MCP access token. Headless clients can use the scoped developer-token method described in the MCP setup guide.