Accounts and multi-tenancy

One deployment of herbe.calendar can serve multiple organizations as separate tenant accounts. Each account has its own connections, members, settings, and data — accounts don't share any calendar data with each other.

Account management is super-admin only, available at /admin/accounts.

Creating an account

Click + New Account and enter:

• Display name — shown in the account switcher and admin header.
• URL slug — used in internal routing. Use a short, lowercase identifier (e.g. burti, flex-bi).

The new account starts empty with no connections and no members. Configure it by opening the account detail page, which presents the same Config screen as the default account.

Members

Users are added under Admin → Members. Members sync automatically from the configured sources (ERP and Azure AD / Google Workspace) the first time any user loads the calendar. You can also add members manually.

Each member has a role:

• Admin — can access the admin panel, manage connections, and invite other members.
• Member — can use the calendar but cannot access admin.

Toggle roles and active/inactive status from the members table. Deactivating a member prevents login but preserves their favorites and shared links.

Person codes

herbe.calendar links each member's ERP user record, Azure AD account, and Google account into a unified person_code. This is what drives the person selector — selecting a person shows their events from all sources simultaneously.

If a member appears multiple times (e.g. because their email differs between ERP and Azure), the Admin → Members page shows duplicate candidates. Use the Merge action to combine them into one entry.

API tokens

Accounts can have API tokens for BI export tools and external integrations. Manage at Admin → Tokens. Each token has a name, scope, and optional expiry. The token value is shown only at creation — copy it immediately.

See Analytics and BI for how to use tokens to export data.