Organization & team

Organization lifecycle, settings, team roles, and end users.

Your organization is the top-level tenant. It scopes API keys, team members, end users, configuration, webhooks, client portfolios, and your private Clarity data. This page covers the organization lifecycle, who can access the admin panel, and how end users differ from your team.

---

Lifecycle

New organizations are created from onboarding or organization settings and start in PENDING. Motif must activate an organization before API and SDK access works.

PENDING → ACTIVE → SUSPENDED / DEACTIVATED → OFFBOARDED
PENDING → REJECTED

Status	API / SDK access	Admin sign-in
PENDING	Blocked	Allowed
ACTIVE	Allowed	Allowed
SUSPENDED / REJECTED / DEACTIVATED / OFFBOARDED	Blocked	Blocked

---

Settings

Setting	Description
Name & logo	Display identity in the admin panel and partner surfaces
Domain auto-assign	Automatically add admins who sign up with your configured email domain
Team roles	Owner / admin / member access for the admin panel
Status controls	Motif-managed lifecycle gates for API access

Other organization-level configuration lives on its own pages: API keys, AI providers, Webhooks, Clarity, and portfolio branding.

---

Access model and roles

Admin access is session-based. Membership and permissions come from roles:

Role	Access
Owner	Full organization administration, including owner-only settings
Admin	Administrative operations: config, API keys, users, portfolios, reports
Member	Member-level dashboard access where enabled

To invite a team member, go to Team, click Invite member, enter their email, and choose a role. They accept by signing in to the admin panel. You can change roles or remove members later. Keep at least one owner. Domain auto-assign adds new admin signups with your company's email domain automatically.

---

End users vs. team members

Three kinds of people interact with Motif. Keep them distinct:

• Team members are your staff, with admin-panel roles above.

• End users are your customers, represented as Motif users and created via the SDK (or manually for testing). They never use the admin panel. The B2B Users area lets admins browse them by name, email, external ID, profiling completion, and strategy/report state, and inspect each user's profile, strategies, reports, and linked portfolio.

• Portfolio customers sign in only to the portfolio app and are blocked from admin endpoints.

Deleting an end user is a destructive operation rather than a soft archive. Treat it as an operational action.