Team & roles

The workspace owner and admins manage membership, roles, groups, and workspace-wide settings. Roles define what actions someone can take; groups define which tickets and areas they work on.

Roles at a glance

Role	Typical responsibilities	Availability
Owner	Billing, domain auto-join, workspace transfer	One per workspace
Admin	Full Studio, team management, all ticket actions	All plans
Manager	Studio + team management (configurable)	Pro / Enterprise
Team lead	Senior agent; group leadership	Pro / Enterprise
Agent	Submit requests and/or handle tickets — scope via groups	All plans

There is no separate “employee” role. Everyone invited is an agent, team lead, manager, or admin. Members who join via domain auto-join are agents and land on Home by default. Use Employee view / Agent view in the profile menu to switch perspectives.

Roles vs groups

Layer	Answers the question
Role	What can this person do? — Studio access, merge, delete, invite others
Group	What can they see and work on? — areas, forms, ticket queues

A user needs both the right role and the right group (or form permission) to handle a ticket end to end.

Inviting members

Team → Members → Invite member

Enter email and display name.
Choose a role (only the owner can assign admin).
The recipient accepts via the email link and sets a password (or signs in with OAuth if enabled).
Resend or revoke pending invites from the same screen.

Domain auto-join

The owner can enable auto-join for a verified company domain under Team → Workspace settings. New sign-ups with a matching email become agents automatically. Public email domains (gmail.com, outlook.com, etc.) are blocked for security.

Groups

Team → Groups organize members for:

Area permissions — who sees which Home categories
Form permissions — who may create or handle specific forms
Routing — auto-assignment and approver pools

Create groups before configuring complex area or form rules — it keeps permissions maintainable as the team grows.

Studio access

Role	Studio (configuration)
Admin	Always
Manager	Yes by default
Agent	Only when Studio access is enabled on their profile

Studio is where admins configure areas, categories, forms, custom fields, workflow statuses, and API keys.

API keys (Pro / Enterprise)

Admin → API lets workspace admins create scoped API keys for integrations (tickets:read, tickets:write). Keys are workspace-bound; usage is visible under the Usage tab.

Documentation: Public REST API and API Reference on docs.flowmingo.io.

Workspace settings (owner)

Under Team → Workspace settings:

Domain auto-join — verified company domain
Member profile — allow avatar / display name changes
Branding — workspace name, logo, accent color (visible on Home and emails)

Custom domains for the web app are configured separately (owner / admin, plan-dependent).

Multiple workspaces

A single user account can belong to several workspaces. Role and group membership apply per workspace — switching workspaces uses the workspace picker after sign-in.

Plan changes

If you downgrade and a role is no longer available on the new plan, affected members are moved to agent until you upgrade again. Review Team → Members after any plan change.

FAQ

How do I preview the employee experience?
Profile menu → Employee view. Switch back to Agent view for Tasks and Dashboard.

Can agents invite other users?
Only if their role includes team-management permissions (typically admin or manager).

Who can delete tickets?
Agents and admins with the ticket delete permission (configurable per role in Studio → Roles).

Areas — visibility and structure
Tickets — day-to-day ticket work
Public REST API — integrations and API keys