Skip to content
TixFin

Teams & roles

Clear responsibilities, even at scale

Every organizer is its own tenant. Inside it, platform roles, project roles and custom role templates decide exactly who can do what.

Get started freeAll features

In short

How does multi-tenancy work?

Every project is an independent organizational space with its own team members, settings, branding and shop identity, so several organizers or brands run in parallel on one platform. Access is steered through global and project-level roles — platform roles such as owner and admin, project roles such as project owner, admin and staff, and custom role profiles built from templates. The permission catalogue is maintained in German and English on both frontend and backend, so role and permission screens never show a mixed language state.

  • Each project is its own tenant

  • Platform roles, project roles and custom templates

  • Bilingual permission catalogue, front and back end

Capabilities

Governance that survives growth

  • 01

    Projects as tenants

    A project owns its members, settings, branding and shop identity, which is what lets multiple brands share a platform without sharing data.

  • 02

    Members and invitations

    Add and remove members, assign a role per member, and send, accept, decline or revoke invitations.

  • 03

    Layered roles

    Platform roles, project roles and custom role profiles from templates cover everything from an owner to a single-purpose door account.

  • 04

    Fine-grained permissions

    Individual rights such as LOYALTY_MANAGE, TICKET_TRANSFER_MANAGE, ROLE_TEMPLATES_MANAGE and the OPS_* family are assignable to custom roles.

  • 05

    Consistent role matching

    Role checks accept variants such as project_owner, PROJECT_OWNER and hyphen or underscore spellings, so custom permissions and feature gates never hide a feature by accident.

  • 06

    Admin audit trail

    Refund requests and refunds, ticket status changes, role and invitation changes, role template changes and discount campaigns are logged centrally and visible as an audit trail.

Specifications

Key facts

Tenancy model
One tenant per project, with its own members, settings and branding
Role layers
Platform roles, project roles and custom role templates
Invitation flow
Send, accept, decline and revoke
Catalogue languages
German and English, frontend and backend
Audit coverage
Refunds, ticket status, roles, invitations, role templates, discount campaigns

Teams & roles

Who did what, on the record

Important administrative actions are logged centrally and retrievable through the admin audit API as well as visible in the dashboard. That is what makes delegation safe: you can hand out a permission without losing the ability to reconstruct what happened.

How it works

Structuring a team

  1. 01

    Create the project

    The project becomes its own tenant with members, settings, branding and shop identity.

  2. 02

    Invite members

    Send invitations, which can be accepted, declined or revoked, and assign a role per member.

  3. 03

    Build custom roles

    Start from a role template and grant only the fine-grained permissions that role actually needs.

  4. 04

    Review the trail

    Use the audit trail to see refunds, status changes, role changes and discount campaigns after the fact.

Use cases

Built for

FAQ

Team questions

Ask the team

  • Yes. Each project is an independent organizational space with its own team members, settings, branding and shop identity, so multiple organizers or brands operate in parallel on one platform.

  • Yes. Beyond platform and project roles, custom role profiles are built from templates and can receive fine-grained permissions individually.

  • Yes. Project permissions are presented in German and English on both frontend and backend, so role and permission screens never mix languages.

  • Yes. Refund requests and refunds, ticket status changes, role and invitation changes, role template changes and discount campaigns are logged centrally, retrievable through the admin audit API and visible as an audit trail in the dashboard.

Give your team the right access

Create a project, invite your team and hand out exactly the permissions each role needs.