Super Admin Guide

Screenshots

Screenshots show demo data from a test environment.

As a Super Admin, you have the highest level of access in Billettsalg. This guide covers the tools and responsibilities unique to your role — the things only you can do.

Your Role

Super Admins operate at the system level — across all organizations, all users, and all events. You can do everything an Admin can within any organization, plus:

• Create and manage organizations
• Manage all users across the system
• Assign users to organizations and set their roles
• Promote or revoke Super Admin privileges
• Impersonate users for troubleshooting
• Set organization capability mode and recover an abandoned mode operation

INFO

For event management, member management, reports, and other organization-level features, see the Admin Guide. This guide focuses on the cross-organization tools only available to Super Admins.

---

Organization Management

Navigate to Super Admin → Organizations (under the 🎼 Super Admin section in the sidebar) to manage all organizations in the system.

Viewing Organizations

The organizations page separates ordinary organizations from Development organizations assigned to your workspace. Each section shows its visible count and a table with:

• Organization name
• Description
• Created date
• Actions — Manage and Delete

The organization name is also a quick-switch link. Click the name to make that organization your current one and go straight to its home page. Use Manage when you want the organization detail page instead.

Development workspace visibility

At the bottom of an organization's detail page, expand Development workspace visibility to mark it as Development and select the existing Super Admins whose workspaces should show it. This section starts collapsed. Confirm before saving. To return it to ordinary visibility, clear the Development marking and save.

This setting only tidies organization lists, section counts, organization-name search and organization choices, including Shared Event and delegated-sales discovery. It does not grant membership or restrict access. All Super Admins retain direct URL/API access, and existing members and E2E identities keep their access. Existing membership records and impersonation choices remain visible in user management. Reporting, event test-data markings and financial records are unchanged.

Every Super Admin can enable Manage all organizations, including hidden Development organizations on the organization overview. Open Manage for a hidden organization to restore its visibility or change its assignments. Hidden rows do not offer a workspace quick-switch link.

An empty assignment is allowed, with a warning. If all assigned administrators have been removed or lost their Super Admin role, use the same recovery view, clear stale assignments and select current administrators. No organization is automatically marked as Development.

Workspace lists refresh after local visibility changes, on account or impersonation changes, and when the window regains focus. If your selected Development organization is no longer assigned to you, the selection is cleared with an explanation. This does not revoke direct access. If another administrator changes the settings while you are editing, reload before saving again.

Creating a New Organization

1. Click Create Organization
2. Enter the Organization Name (required)
3. Optionally add a Description
4. Click Save

The organization is created immediately. You can then add members to it from the Users page.

Managing an Organization

Click Manage on any organization to see its detail page. From there you can:

• Expand Members to view members and their roles. Choose Manage beside a member to see details, change their role or remove them. The member count remains visible while the list is collapsed
• Open Manage organization to edit the name, description and type together
• Change the organization between full and limited sellingPartner mode
• Inspect and recover stale owner-state coordination
• See organization-specific data

Editing organization details:

1. On the organization detail page, click Manage organization.
2. Edit the display name (1–255 characters), description (up to 2,000 characters) and organization type. An empty description clears the existing description.
3. Click Save to save all three fields together. Capability mode and Development visibility are not part of this save.

Cancel closes the panel without saving. If you have unsaved changes, confirm that you want to discard them. A failed save keeps the draft visible for correction or retry.

The page shows the saved organization details. Renaming also refreshes your session's organization names and organization choices. Other signed-in users pick up the new name when their own session refreshes. The organization identifier and stored records do not change.

Members, Invitations and the Development visibility panel start collapsed. Adding or importing members opens the member list so you can see the result. Development visibility remains at the bottom of the page with its own separate save.

INFO

• People already signed in to that organization may keep seeing the old name in cached menus/labels until they refresh their session or sign in again.
• Existing invitation links keep showing the organization name that was current when they were created (point-in-time snapshot) — that doesn't change even when the invitation is later accepted.
• New invitations created after the name change use the updated display name.
• Changing the display name does not affect internal organization IDs, data partition keys, member lists, order/event history, or past feedback/notifications.

Changing organization capability mode

On the organization detail page, open Manage organization and use Capability mode. Select the new mode, choose Apply mode change, then confirm. This is a separate operation: it neither saves nor discards drafts in the name, description or type fields. Recovery information remains visible on the detail page even after the panel closes.

• Full — the organization can own events, manage external sales, invite selling partners, and create or join Shared Events.
• Selling partner — the organization keeps members, roles, settings, notifications, delegated invitations, member ordering, approval and delivery, returns, and partner-scoped Overview, Orders, and Reports. It cannot own or operate events and cannot participate in Shared Events.

Changing sellingPartner to full is an explicit upgrade and is always allowed. Changing full to sellingPartner is a downgrade and succeeds only after the server proves that the organization:

• Owns no events, including soft-deleted events
• Has no Shared Event participation
• Is not still the owner of an invited or active selling-partner delegation

The downgrade fails closed if a dependency check cannot complete. It also coordinates with owner-state creation, so a mode change cannot race with an event, Shared Event, external-sale, or outbound-delegation write. This coordination uses authoritative reads, ETag conditions, transition markers, and leases across existing documents; it is not a cross-container transaction.

Limited organizations are excluded from Shared Event participant search but remain eligible in selling-partner discovery. They can still decline, leave, or be removed from Shared Event state so the mode never traps an organization.

Recovering an abandoned operation

The detail page lists active mode transitions and owner-state leases. An operation is marked stale only after its five-minute coordination window expires. Do not clear an operation merely because it looks slow.

For an operation that is demonstrably stale:

1. Reload the coordination state.
2. Verify the exact operation kind and operation ID.
3. Enter a reason of at least three characters.
4. Confirm Recover.

The request includes the operation kind, operation ID, and the ETag from the state you reviewed. The server clears only that exact stale operation. If the organization changed, the request returns a conflict and the page reloads the current state. Recovery never changes the organization mode and never skips downgrade dependency checks; rerun the downgrade afterward.

Explicit force recovery

Recovery removes a stale safety marker or lease. Use it only after you have verified that the original operation is abandoned. The app records privacy-scrubbed audit telemetry with the organization, operation, actor, outcome, and bounded operator reason.

Deleting an Organization

Click the Delete button on an organization row and confirm. This removes the organization and its associations.

WARNING

Deleting an organization is a significant action that cannot be easily undone. Make sure all events are concluded and financial data has been exported before deleting.

---

User Management

Navigate to Super Admin → All Users (under the 🎼 Super Admin section in the sidebar) to see every user in the system.

Viewing Users

The users table shows:

• Name and email
• Assigned organizations with their role in each (e.g. "Oslo Organization (admin)")
• Created date
• Super Admin badge — indicating whether the user has system-level access

Use the search box to filter users by name, email, or organization name.

Adding a New User

1. Click Add User
2. Enter their email (required) and name (required)
3. Optionally assign them to an organization and select their role (Member or Admin)
4. Click Add

CSV Import

For bulk user creation:

1. Click Import CSV
2. Download the template to see the expected format
3. Prepare your CSV with user details
4. Upload and review the import results

INFO

Both comma (,) and semicolon (;) separators are supported. Header rows are auto-detected.

Editing a User

Click the Edit button on a user row to open the edit dialog. You can update:

• First name and last name
• Email
• Phone (optional)
• Organization assignments — add or remove the user from organizations, and set their role in each organization (Member, Ticket Manager, Treasurer, or Admin)

Promoting / Revoking Super Admin

To make someone a Super Admin (or remove the privilege):

1. Find the user in the list
2. Click the Super Admin badge toggle in their row
3. Confirm the action

WARNING

Super Admin access is powerful — it gives full control over every organization and every user. Only promote trusted individuals.

Assigning Users to Organizations

You can assign users to organizations in two ways:

Individual assignment:

1. Click Edit on the user
2. In the organization assignments section, add a new organization and select their role
3. Save

Bulk assignment:

1. Select multiple users using the checkboxes
2. Click the Bulk Assign to Organization action
3. Choose an organization and role
4. Confirm

Bulk Operations

Select multiple users with the checkboxes (or use Select All for the current filtered view), then:

• Bulk assign to organization — Add all selected users to an organization with a specific role
• Bulk delete — Remove all selected users (with confirmation showing the count)

WARNING

Bulk delete cannot be undone. Double-check your selection before confirming.

---

Impersonation

Impersonation lets you see the app exactly as another user sees it — their events, orders, history, and permissions. It's your go-to tool for troubleshooting when a user reports a problem.

What It Is

When you impersonate a user, the app switches to show their data — their events, orders, history, and permissions. You see what they see, in the context of their organization and role.

Use responsibly

All impersonation sessions are logged and audited. Every action you take while impersonating is recorded with your admin identity. Use this feature only for legitimate support and troubleshooting purposes.

When to Use It

• A member reports they can't see their orders → impersonate them to check
• Verifying that a new member's setup looks correct
• Debugging role permission issues
• Confirming what data a specific user can access

How to Start Impersonation

1. Go to Super Admin → All Users
2. Find the user you want to view as
3. Click the Impersonate button (👤) in their row
4. If the user belongs to multiple organizations, select which organization context to use
5. You'll be redirected to the home page, now viewing as that user

The Impersonation Banner

While impersonating, a prominent banner appears at the top of the screen:

"Viewing as [User Name]" — view-only

This banner is always visible as a reminder that you're in impersonation mode. A notice also reminds you that actions like ordering tickets are disabled — impersonation is view-only.

Stopping Impersonation

Click Stop Viewing in the impersonation banner to return to your own account. You'll be taken back to the Super Admin view.

Direct Super Admin Ticketmaster corrections

Select an organization and use the same Correct sale button and correction dialog as an organization administrator. You act as your actual signed-in Super Admin identity, which is audited with the selected organization and your correction reason. You do not select an organization administrator or start an impersonation session. View as User remains read-only.

Explicit rollout required

The server setting PLATFORM_SUPER_ADMIN_EXTERNAL_CORRECTIONS_WRITE is off by default. An authorized operator must explicitly approve and enable it together with the existing SALES_CORRECTIONS_EXTERNAL_WRITE gate, after deployment and review. The frontend unified correction workflow must also be enabled. Selecting an organization never enables these settings. The separate PLATFORM_SUPER_ADMIN_CORRECTION_IMPERSONATION setting is unchanged and is not required for this direct flow. See the environment reference.

1. Stop any View as User session and select the organization you intend to support.
2. Open Ticketmaster and select the event and showtime. The app verifies correction capability for your current organization before making Correct sale available on ordinary allocated sales.
3. Select Correct sale, review the verified categories and quantities, enter your reason, and save through the existing correction dialog.

Loading, disabled, denied, or unavailable capability never grants correction access. Use Refresh correction access to check again. Checking capability does not open a dialog, preview a correction, or change a sale. Changing organization, event, showtime, signed-in identity, token, or relevant session context closes an open correction draft with a notice. Loss of permission also closes the draft. A normal focus change preserves a current draft. Restoring access never submits the previous correction automatically. A context change cannot undo a request already sent.

The UI does not automatically retry correction requests for transient server or network failures. After a 401 authentication response, the API client may resend the request once if your sign-in token has changed or a session refresh succeeds. If an access error remains, restore access before explicitly retrying the correction.

What's Logged

Every impersonation session creates an audit record with:

Field	Description
Admin	Who initiated the impersonation (you)
Target user	Whose account was viewed
Start time	When the session began
Stop time	When the session ended
Session ID	Unique identifier for the session
Action	Start or stop event

---

Audit Logs

Navigate to Super Admin → All Users and review impersonation history to see a record of all impersonation sessions.

What's Tracked

The audit trail records:

• Which Super Admin started the impersonation
• Which user was impersonated
• The target user's email and role at the time
• Session start and stop timestamps
• Total session duration
• A unique session ID linking the start and stop events

INFO

The legacy view-only flow sends its start and stop audit events automatically. Audited correction sessions are different: the server persists and verifies their authoritative session transitions. A failed activation never grants correction access, and a failed end request does not count as a confirmed end. Direct Ticketmaster corrections do not start these sessions; their audit actor is the signed-in Super Admin, not a selected organization administrator.

---

Tips for Super Admins

Setting up a new organization

1. Create the organization from Super Admin → Organizations
2. Add or assign users from Super Admin → All Users
3. Promote one user to Admin role within that organization
4. The new Admin can then create events and invite members

Quick troubleshooting workflow

1. User reports a problem
2. Find them in Super Admin → All Users
3. Impersonate to see what they see
4. Stop impersonation
5. Fix the issue (role change, organization assignment, etc.)
6. Confirm with the user

---

Need Help?

• Admin features — See the Admin Guide for event management, members, reports, and more
• Getting started — See Getting Started for login help and role overview
• Technical issues — Check the Architecture Reference for system details