Organizations
The shared workspace that owns your Events, people, money, and public identity
An Organization is the workspace your team signs in to. It owns every Event, Pass, Order, Member, and setting, and it is the name buyers see on a public Event page.
One Organization suits one business. You need a second one when two brands must keep separate money, separate teams, and separate public pages.
What lives inside one
| Area | What the Organization owns |
|---|---|
| Events | Drafts, published pages, EventSessions, EventGroups, and EventSeries |
| Selling | Passes, Orders, refunds, invoices, and payouts |
| People | Members, invites, Roles, and scoped Role assignments |
| Money rules | Preferred currency, platform fee, tax identity, payout country |
| Reach | Custom domains, verified email domains, identity providers, tracking pixels |
| Identity | Name, description, logo and icon, accent colour, links, contact details |
Everything is owned by exactly one Organization. An Event cannot be moved to another one, and a buyer never sees two Organizations' data mixed together.
Creating your workspace
Creating an Organization makes you its Owner and seeds five Roles for you to assign. The response returns the Organization and your membership in one object.
Pick a name and a slug. The name holds up to 160 characters. The slug becomes your dashboard address and defaults to a readable version of the name plus a short random suffix.
Send an Idempotency-Key header. A retry with the same key and the same details returns the original result instead of creating a duplicate. The same key with different details is rejected with a conflict.
Land in the workspace. You are the Owner, with every Capability, and the five starter Roles are ready to hand out.
Slugs are global, not per-Organization: two Organizations can never share one. A slug is 3 to 63 characters of lowercase letters, digits, and hyphens, must start and end with a letter or digit, and cannot be one of the reserved host words such as app, api, docs, or www.
Creation is rate limited to five attempts per Account in fifteen minutes. That limit exists to stop runaway scripts, not to ration real teams.
The profile buyers see
The public organizer card on an Event page is deliberately small. It carries the name, the description as a short bio, the icon, the website, the five social links, contact email and phone, and the accent colour.
Name
Up to 160 characters
Shown on every public Event page
Bio
Up to 500 characters
The Organization's description field
Icon
Square mark
Only the icon is published
Accent
One hex colour
Used for public tinting where a poster is missing
Social links
Five channels only
Instagram, X, LinkedIn, Facebook, YouTube
Contact
Email and phone
Phone must be in international +country format
The public card never includes your currency, fees, tax number, payout country, suspension state, or membership list. Those stay inside the workspace.
Two rules catch people out. The logo and the icon are separate uploads, and only the icon is published. Social links are a closed set: an unknown channel is rejected rather than stored, and every value must be an absolute http or https address.
Settings only your team sees
General settings hold the timezone (an IANA name such as Asia/Kolkata), a default location city, contact details, website, and social links. A new Event takes its venue city, state, and country from the commercial tax profile instead.
Tracking settings hold up to four client-side pixel IDs. All four are optional, and consent is on by default.
All four IDs share one rule: up to 64 characters drawn from letters, digits, hyphens, and underscores. Vendor formats are not checked more tightly than that.
| Field | Typical value |
|---|---|
| GA4 ID | G-XXXXXXX |
| Google Tag Manager ID | GTM-XXXX |
| Meta Pixel ID | A number; digits are not required |
| TikTok Pixel ID | Letters and digits |
| Consent required | On by default; when on, pixels load only after consent |
Finding and switching
One Account can belong to several Organizations. The dashboard lists them, and the memberships endpoint returns each Organization with the Role keys you hold there, so a client can show the right workspace picker without a second call.
Names, slugs, and descriptions are editable later. Changing the slug changes your dashboard address.
Suspension is a platform action
Ulsav staff can suspend an Organization. While suspended, no member can authorize anything, reads included. The Organizations API answers organization_suspended; other areas treat the caller as a non-member and return their own not-found or forbidden error. Nobody inside the Organization can lift it.
What you cannot do
- Delete an Organization. There is no delete operation; history, invoices, and Orders must remain readable.
- Remove the last Owner. The request fails with
last_owner_required.
Leaving is not a separate action. A member who holds the member-removal Capability can remove their own membership like any other, and a member without it can remove nobody.
Related
- Members — inviting people and removing them
- Roles — what each person is allowed to do
- Commercial Profile — currency, fees, and tax
- Domains — custom hostnames and email domains
- Events — what an Organization publishes
- Capabilities — the full permission catalogue