Administering Miseline

This guide is for owners and admins: how the account is structured, who can do what, and where the organization-level controls live.

Organizations and sites

Your organization is the account: it owns the people, the data, and the plan. Inside it, sites are physical operations — a kitchen, a café, a dining hall, a venue. Menus are assigned per site, production is planned per site, boards belong to a site, and "today" is always computed in the site's own timezone.

Manage both from Insights → Settings:

• Organization — rename the organization.
• Sites — add sites with a name, short code, address, and timezone; define spaces (rooms, stations, storage areas) within each site; archive sites you no longer operate.

Multi-site groups that manage other organizations' programs can run as an operator: an operator organization has client organizations beneath it, each with its own sites, staff, and data. Operator admins get a cross-client executive roll-up; client data otherwise stays inside the client organization.

People, roles, and permissions

Invite people from Settings → Users. If the person doesn't have a Miseline account yet, one is created and they're emailed a temporary password to change at first sign-in.

Each member has one role in the organization. Roles are ranked — each level includes everything below it:

Two refinements:

• Site scoping — a membership can be limited to specific sites; leave it empty to grant all sites.
• Credentials — professional credentials attach to a membership independent of rank: RD (Registered Dietitian), ServSafe, and CDM. Some actions check credentials, not just role — for example, approving a menu or diet-related signoff requires the RD credential no matter how senior the account.

Billing and plans

Insights → Billing & plan (owners) shows your current plan, live usage meters (sites, boards and devices, AI tokens this month, team members, diners), and the available plans. Every new organization starts on a 30-day Pro trial. Switching plans is self-serve; when a feature isn't included in your plan, the app shows exactly which plan unlocks it rather than hiding the page.

Plan summary (see pricing for the current details):

• Starter — one site, core operations, remote walkthroughs.
• Pro — multi-site, clinical dining, catering, POS, cost intelligence, automated ordering, the content library, loyalty and campaigns, storefront, the review program, webhooks, and API keys.
• Enterprise — everything in Pro plus exec roll-ups, bring-your-own AI key, marketplace publishing, and social publishing, at the highest site and device limits.

The same page carries the Starter pack installer (re-apply the seeded frameworks, policies, and templates for your vertical), the Developer section (webhooks and API keys), and the Trust section with the admin audit trail — every authenticated change in the organization is recorded with who, what, and when.

Boards and devices

Equipment → Boards & devices (admins) registers non-user screens and hardware: kitchen wallboards, front-of-house menu boards, tray-line displays, site-map screens, kiosks, and sensor gateways. Devices authenticate with their own long-lived token — never a person's login — and pair with a short six-character code typed on the screen. Device counts meter against your plan. See Production and boards for what each board face shows.

AI settings

AI features (recipe import, nutrition estimates, huddle summaries, the assistant, and more) are optional everywhere — every AI feature has a manual path, and if AI isn't configured the app says so politely instead of breaking.

• By default, AI runs on platform-managed keys with a monthly token budget per organization, metered on the Billing page.
• Enterprise organizations can bring their own AI key (Agent settings) so usage runs on their own account.
• Transcription (huddles, interviews) can point at a custom speech-to-text endpoint under Settings → Interview & huddle transcription, with a built-in "Test endpoint" probe.
• The in-app Assistant is configured from Agent settings: name it, set its accent color, and control which staff see it.

Language and notifications

• The web app and staff app are fully bilingual English / Spanish — each person picks their language in Settings, and board screens can be set per device.
• Settings → Notifications and the SMS section control per-user notification and text-message preferences (a phone number is required for SMS; escalation policies decide who gets woken up when an alert goes unacknowledged).

Organization branding

Your primary and accent colors theme kitchen boards, menu boards, and diner-facing screens, so each program's boards look like their own. Set them under Settings → Brand colors — pick a primary and an accent with the live preview, save, and boards apply them on their next refresh. (They're also settable through the API as organization settings.)

Data protection notes

• Every request is scoped to your organization; members only ever see their own organization's data (site-scoped members, only their sites').
• Passwords are stored hashed; sessions use short-lived tokens with rotating refresh tokens; changing a password signs out all other sessions.
• Public links (shared quotes and invoices, survey links, inspection reports) are sanitized capability URLs — they carry no login and expose no internal identifiers. Treat them like the documents they are: anyone with the link can view.