Organisation and account

An organisation is the ownership and billing boundary in Serversinc. Its members share access to the organisation’s servers, applications, databases, provider credentials, storage providers, integrations, and activity.

Your account can belong to more than one organisation. Always check the current organisation before making a change through the dashboard, CLI, API, or MCP server.

Manage members

Organisation owners and authorised members can invite people as member or admin. Invitations remain pending until accepted and expire if they are not used.

From organisation settings, you can:

• Review current members and roles
• Invite a member
• Review and revoke pending invitations
• Remove a member
• Leave an organisation when ownership rules allow it

The current product caps organisation membership at ten people. Removing someone revokes their access to the organisation; it does not delete the resources they created.

Connect cloud providers

Provider keys let Serversinc provision new servers for the organisation. Add credentials only for providers you intend to use, and grant the minimum provider-side permissions required for provisioning and lifecycle operations.

Tokens are masked after storage and cannot be retrieved from the dashboard. Removing a provider key does not automatically remove servers already created with it, but future provider operations may fail.

Cloud provider credentials and backup storage credentials are separate. Storage providers are configured for database and volume backups.

Connect GitHub

Install the Serversinc GitHub App on the organisation to deploy from repositories. The installation can cover every repository in the GitHub account or only selected repositories.

Organisation members use the shared installation when creating GitHub applications. If GitHub suspends the installation or it is disconnected, existing containers keep running, but new repository builds cannot start until access is restored.

Manage repository selection on GitHub rather than by storing a personal OAuth token in Serversinc.

Secure your account

Two-factor authentication

Serversinc supports authenticator-app codes using TOTP. During setup, scan the QR code, confirm a code, and save the recovery codes before closing the dialog.

Recovery codes are shown as credentials, not reminders. Store them outside the device used for two-factor authentication. Regenerating them invalidates the old set.

Active sessions

Account settings list active browser and CLI sessions with their type, network address, and last activity. Revoke an unfamiliar session or revoke every other session while keeping the current browser signed in.

API tokens

Create personal access tokens for the REST API, CLI, and MCP server. A token can have an optional expiry and is shown once at creation.

Name tokens after their use, such as production-deploy rather than token-1. Revoke tokens that are unused, exposed, or attached to a retired integration.

Review organisation activity

The activity feed records changes across the organisation. Each entry identifies when possible:

• The actor
• The action
• The affected resource
• The time

Filter by resource type to investigate a server, application, deployment, database, or backup change. Activity created by a queued job or webhook may be attributed differently from a direct dashboard action.

The feed is an operational history. Do not assume it replaces a formal compliance audit log unless the retention and event coverage meet your requirements.

Manage billing

Billing belongs to the organisation. The billing page shows subscription status, managed server count, renewal or cancellation date, and invoices.

Use the billing portal to update payment details or manage the subscription. A past-due subscription restricts access until the open invoice is paid or the payment method is updated.

Hide sensitive data

The appearance settings can mask sensitive values, such as server addresses, in the dashboard. You can reveal a masked value temporarily where the interface allows it.

This is a screen-privacy preference, not an access-control boundary. Anyone with permission to the underlying resource may still retrieve it through another supported interface.

Next steps

• Servers: connect or provision infrastructure for the organisation.
• Automation: use API tokens with the CLI, REST API, or MCP server.
• Reference: review roles, resource scope, defaults, and limits.