docs
/
Studio Manager

Studio Manager

The console you sign in to — what each area does, and how the whole surface fits together.

Studio Manager is the console. Everything you configure, build, sell, staff and report on happens here, and it all acts on the same records the API, the mobile app and the event platform use.

This page is the map. Each area below has its own section.

The console at a glance

Studio Manager's sidebar has thirteen areas, plus trash.

AreaWhat lives there
App RootInbox, analytics, dashboard builder, activity feed, domains, sites and dev environments, services, service pricing, setup wizard
Build StudioWeb pages, forms, presentations, graphic design, root page, templates
DAMContent Studio — posts, multi-page documents and courses — plus categories, navigation, tags, comments, documents, site notices, message templates
StorefrontProducts, orders, subscriptions, invoices, shipping, pricing, returns, discounts, gift cards, cart, inventory, rental, attributes, brands, sales channels
CRMLeads, marketing and ads, social, broadcast, promotions, merchant accounts, affiliates, phone and SMS, email accounts, tickets, events, reservations, forms, calendar, customer activity, chat
AI, IVR & AutomationAI assistant, IVR and phone system, automation, workflow, schedules
EventsEvents, sessions, ticket types, tickets, bookings, badge templates, speakers, exhibitors, check-ins, leads
LogisticsDelivery zones, agents and jobs
FinanceWallets, payouts, wallet transactions, payments
CommunityPages, feed, stories, connections, messages, groups, meetings, announcements, badges, hashtags, moderation, notifications
DatabaseCollections, sub-schemas, import and export, data explorer
ConfigurationSettings, business locations, users and groups, roles and permissions, password policy, integration config, scripts, translation, blacklist
AccountProfile, billing, API keys, usage, upgrade, logs

Each area opens on its own dashboard, so entering a section gives you its current state before you drill into a specific screen. The figures are computed on the server (GET /studio-overview/:section — see Platform operations).

How navigation adapts

The console does not show everyone the same menu. What appears is decided by the signed-in user's roles.

Each role carries a menu include and exclude list alongside its permissions, so a warehouse user and a finance user sign into the same console and see different consoles. This is configuration, not separate builds — see Configuration.

Hidden is not the same as blocked

Menus adapt for usability, but access is enforced on the server. Hiding an area does not grant a shortcut around its permissions, and revealing one does not bypass them.

AI quick bars

Screens with an AI helper — Build Studio, Creative Studio, Content Studio posts, collections, leads and the lead prospector, marketing, broadcast, message templates, compose, automation, IVR and data visualisation — show it as a quick bar floating at the bottom right, clear of the approvals tab on the right edge. Minimise a bar and it becomes a slim tab on the right edge, like the approvals tab, with a dot while the assistant is still working. The choice is remembered per bar, so a bar you put away stays away on the next visit.

Console header and help

The strip across the top of the console holds the controls that do not belong to any one area. Left to right:

ControlWhat it does
Close all (✕, far left)Closes every open window and panel, then goes back to the app you used before this one — see Close all
Screen controlsA few screens add their own controls here: Build Studio its editing tools, Inbox its channels, Workflow its tabs
LanguageThe admin interface's language — see Language
PhoneThe browser softphone — see Phone, SMS & IVR
Live chatConnect to the chat desk, open it, or go offline — see the agent desk
AI employeesWhich AI employees are online, with one click to chat with one or open it. Hidden for anyone who cannot manage AI employees
AI AgentOpens the AI agent panel
What's this?Point-and-explain help — see What's this?
SupportThe help menu — see Support menu
Report a BugSends a bug report to Appmint — see Report a bug
Notifications (bell)Approvals waiting on you, notices and alerts — see Notifications
Share workspaceNot active yet — see Share workspace
Sign out (power icon)Ends the session

Support menu

Support opens a short menu:

  • How do I…? — search a library of how-tos ("Connect my domain", "Add a product to sell", "Invite my team"…). Picking one runs a guided tour over the real screens, so it ends with you on the right screen with the right control lit up. When nothing in the library matches, the question goes to the AI agent instead.
  • Interface tour — a walkthrough of the whole console: the sidebar, each area, and the controls in this header.
  • Documentation — opens this documentation in a new tab.
  • Submit Ticket — a form with a subject, priority (low, medium or high), description and attachments; subject and description are required. The ticket is created as a support ticket in your own organization's tickets.
  • Live Chat — opens a chat with Appmint support.

What's this?

Click What's this? and the cursor becomes a question mark. Hover to see what you are about to ask about, then click anything on screen to get an explanation of it. While it is on, clicks are captured rather than acted on — pointing at Delete explains Delete instead of deleting. Where there is no written explanation for a control, Ask the AI hands its label and the current screen to the AI agent. Click the button again, or press Escape, to stop.

Notifications

The bell's red badge counts what is new for you: unread notices, your own unread lines and approvals waiting on you. It opens a panel with tabs:

TabWhat is in it
Waiting on youApproval tasks assigned to you. Approve or decline straight from the row, or open it to add a note, hand it to someone else, or escalate it
MineYour own lines, newest first — decisions, assignments and access changes that concern you
NoticesEverything sent to the organization, by the platform or by your own admins, filterable by All, Unread or Platform. A notice you dismissed can be read again here, and opening an unread one marks it read
AlertsThis session's pop-up messages; Clear empties the list. They are gone on reload

The same panel also opens as a window of its own, from the bell on the setup dashboard.

Close all

When the screen has filled up, Close all clears it in one click. It closes every open window and panel first, then steps back to the app you were using before the current one; if there is none, it opens the current section's dashboard, and failing that App Root.

Report a bug

Report a Bug is for something that is broken, as opposed to confusing — use What's this? for that. The form asks for a title and a description (both required), and optionally error details and files such as screenshots. The page address is filled in for you, and errors the browser logged while you worked are captured and shown in the form. Browser, operating system, screen and window size are attached automatically.

The report is filed as a high-priority bug ticket with Appmint, not in your own organization's tickets.

Share workspace

The share-workspace button is in the header, but sharing is not built yet: clicking it does nothing.

Language

The language picker in the header shows the language currently in use — English, Español or Français — and switching it applies at once and is remembered in the browser.

Multi-location

Organizations operating in more than one place switch location context in the console. Inventory, staff, schedules, service points and reporting all scope to the selected location.

Locations are defined under Configuration, and most operational areas respect the current selection rather than requiring separate setup per site.

Trash

Deletes across the console are recoverable. Removed records move to trash and can be restored, rather than disappearing immediately.

The two halves

Studio Manager spans two surfaces that share one login and one dataset:

The builder — Build Studio (pages and forms), DAM (Content Studio posts and courses, and the taxonomy around them) and Database. This is where the customer-facing side and the data behind it are made.

The business console — storefront, CRM, events, logistics, finance, community and configuration. This is where the business is run.

You do not choose between them. Which areas appear depends on what your organization has enabled and what your role allows.