Skip to main content

Team vs. members

Your team is everyone with access to the 4D console for your organization. Your members are the people your application tracks - they get wallets, XP, and engagement history, and they never see the console. The two are independent: a team member holds no member profile or wallet, and the same person can be both (a staff member who also uses your app). A team member is one of:
  • An administrator - full console access, including team and role management. Administrators must enrol an authenticator (TOTP) before any privileged action.
  • A role holder - a capability-bounded seat pointing at one of your defined roles (the prebuilt CMO, CFO, and Sponsor templates, or a custom role). A role decides which console pages the holder sees, which data the AI assistant may reach for them, and - for advertising roles - which campaigns they can access.

Managing the team

The console’s Team section lists everyone with access, lets you invite by email (as an administrator or into a role), change or revoke a seat, and review pending invitations. Role definitions live under Team → Roles. Invitations grant console access only - accepting one never creates a member profile, wallet, or XP account. Tracked members are created through POST /v1/users, the engagement SDK, or a CSV import instead. Every organization keeps at least one administrator: the console refuses to demote or remove the last one.

Where to go next

  • Members - the tracked, two-level member identity.
  • Tenants - how organizations are isolated.