User Guides

Administer the portal

Edit page
Manage portal users, organizations, memberships, sessions, and feature access as a system administrator.

System administration is installation-wide. It is separate from being an owner or administrator inside one organization and is granted through the deployment's ADMIN_EMAILS configuration.

Open Admin → Organizations at /admin/organizations or Admin → Users at /admin/users. Both the navigation and server routes require the system-administrator role.

System administrators can alter identities, sessions, organization access, and production feature availability. Use named administrator accounts, keep ADMIN_EMAILS small, and record the reason for sensitive actions in your operational process.

Manage organizations

The organization list can be searched by name or slug and sorted by name or creation date. Select an organization to inspect its details, members, pending invitations, and feature capabilities.

To create an organization:

  1. open /admin/organizations/create;
  2. enter a display name;
  3. review the generated slug;
  4. ensure the slug contains only lowercase letters, numbers, and hyphens;
  5. create the organization, then configure its membership and features.

An organization slug is used in routes and lookups. Change it deliberately and verify links or integrations that may retain the previous value.

On an organization detail page, a system administrator can:

  • edit its name, slug, and logo;
  • enable or disable the Timesheets workspace;
  • enable invoicing when the Timesheets workspace is enabled;
  • inspect client relationships and their access mode;
  • configure organization invoice email when invoicing is enabled;
  • manage members and pending invitations.

Disabling the Timesheets workspace also disables invoicing. It does not delete the organization's existing feature data.

Use Link existing user when an account already exists and needs an organization membership. Select the user and an owner, admin, or member organization role. The portal rejects duplicate membership.

Removing a membership does not delete the user account. The current administrator cannot remove their own membership through this action, and the last owner of an organization cannot be removed.

Use an invitation when the person does not yet have the intended membership. Invitations can be assigned an organization role, resent, or cancelled. A newly created invitation currently expires after two days and requires platform email delivery to be configured.

Manage users

The user list shows name, email, system role, ban state, verification state, and creation date. Search by name or email, then use the row actions for the selected account.

Available actions include:

  • change the system role between user and admin;
  • update the user's name or profile image;
  • set a new password of at least eight characters;
  • inspect active and expired sessions and revoke another session;
  • ban a non-administrator, optionally with a reason and expiry;
  • unban an account;
  • impersonate a user for diagnosis.

The portal prevents changing your own system role, banning an administrator, and revoking your current session from the session manager.

Use impersonation safely

Impersonation replaces the effective browser session and redirects to the dashboard. Every subsequent action is performed as that user until impersonation is stopped.

Before starting, record the support reason and obtain appropriate authorization. Avoid changing data unless the support case requires it, never ask the user for their password, and stop impersonation as soon as the check is complete.

Customer Portal does not currently include a general administrator audit-log interface. Preserve external operational records for role changes, bans, password resets, impersonation, session revocation, and organization capability changes.

For delivery failures, use troubleshooting. For organization-level setup, continue with accounts and organizations or set up a timesheet workspace.