Administration and settings

Understand workspaces, membership, private teams, account preferences and optional external capabilities.

Application revision 8c09715b · Docs d2d4fba5

    Membership and workspaces

    Administrators manage workspace and membership through settings, or choose Add member from the workspace-name menu. Workspace administrators add an existing account by looking up its full email address; they cannot browse the platform-wide account directory. Platform administrators can still select from the account list. If a batch of team members partly fails, the dialog keeps failed people and their reasons without re-adding successful people. Grant the role required for the intended job; ordinary collaboration should not default to administrator access. Removing a member or disabling an account affects subsequent access and does not recall already exported or delivered content.

    Platform administrators can create or edit accounts under Platform users. Names cannot be blank and email addresses must be valid. Passwords must have at least 8 characters and at most 72 UTF-8 bytes. An email already in use, including by a deactivated account, cannot be reused when creating or editing. A new account is not automatically added to any workspace; add it as a member separately. Ordinary users without a workspace can refresh membership, copy their email for an administrator, or sign out. Platform administrators without a member workspace can enter a workspace home from the chooser or open Platform users separately without becoming workspace members.

    Initial setup also requires a valid email, a nonblank name and workspace name, and a workspace URL slug of 2–32 lowercase letters, numbers, or hyphens.

    Resources are isolated by workspace. Project, team and issue associations must remain valid within that scope. Sharing a URL does not grant membership. There is no public signup; administrators provide accounts through the instance’s management process.

    Team settings navigation

    Open Settings from the menu beside a team in the sidebar; this entry is available to administrators. The dedicated navigation groups General and Members under Team, Statuses and Labels under Issues, and Triage and Cycles under Workflows. On narrow screens, use Open settings navigation to open the drawer. Switch team opens another readable team’s General settings; Back to app returns to the current team’s issues. Existing settings links still open their selected category directly.

    Private teams

    Private teams require appropriate membership. Workspace administrators do not automatically bypass that requirement. Projects spanning teams may require visibility into all relevant teams. A visible management button is not proof of current authorization; confirm actual membership.

    API keys inherit their owner’s current permissions. A broader scope cannot exceed the owner’s authority. After revocation, membership removal or account suspension, an old client session is not evidence of continued access.

    Personal preferences

    Manage language, theme, time zone and notifications in account settings. On narrow screens, use the current category button in the settings header to open the category drawer. A saved account time zone takes precedence; otherwise the browser’s zone applies. Time zones affect date filters, cycle boundaries and history charts, so check them before comparing results across locations.

    Personal My issues display preferences and administrator-managed workspace defaults have different scopes. Confirm whether you are changing a shared default or only your own presentation.

    Optional capabilities

    Email requires SMTP, attachments require private object storage, and Webhooks require server encryption configuration and an eligible public HTTPS receiver. Saving a preference does not connect or enable an unconfigured service.

    Production credentials belong in the deployment environment, never in the website, documentation, issues or example API calls. Backup, retention, deletion and recovery policies are the responsibility of the instance operator. The website does not manage the production database. Operators should follow the repository’s operational documentation and approval requirements before deployment or recovery.