Skip to main content

Teams and Organizations

Influgen's enterprise layer is organized around organizations. An organization gives a team a shared operating boundary for members, roles, white-label settings, and audit history.

Organization endpoints​

  • GET /api/v1/organizations
  • POST /api/v1/organizations
  • GET /api/v1/organizations/{id}
  • PUT /api/v1/organizations/{id}
  • GET /api/v1/organizations/{id}/members
  • POST /api/v1/organizations/{id}/members
  • PUT /api/v1/organizations/{id}/members/{userId}
  • DELETE /api/v1/organizations/{id}/members/{userId}

What an organization stores​

An organization can carry:

  • name
  • slug
  • billing metadata
  • logo URL
  • primary and secondary colors
  • membership roster

Each organization response also includes an SSO placeholder object so enterprise customers can see the future integration shape.

[screenshot: Team settings screen with organization identity, member list, invite form, and current user role]

Common workflows​

Create an organization​

The user who creates the organization becomes its first owner.

Invite a member​

You can invite by:

  • email
  • user ID

Each member is assigned a role at invite time.

Update branding​

Organization-level visual fields make it easier to align internal workspaces or prepare for white-label delivery.

Best practices​

  • create one organization per real operating boundary, not one giant catch-all
  • keep ownership tight
  • give editor access broadly only if queue moderation is a shared responsibility