Promptic

Teams and access

Promptic has two membership layers. Organization roles govern the team and billing context; AI Application roles govern access to application data.

Organization roles

RoleIntended use
OwnerFull organizational control, ownership-sensitive actions, and billing administration
AdminDay-to-day member, AI Application, model, and billing management
MemberRegular team participation without organization administration
GuestNarrow access created for people invited only to specific AI Applications

Keep at least one reachable owner and avoid using owner access for routine work.

AI Application roles

RoleIntended use
AdminManage application settings, members, providers, and destructive actions
MemberWork with the application’s components and data without administrative control

An Organization guest must be assigned to an AI Application before they can use its data. Removing their last application membership can also remove their guest Organization membership.

Invite people

  • Invite team-wide collaborators from Organization settings → Members.
  • Invite application-specific collaborators from AI Application settings → Members.
  • Verify the email address and role before sending an invitation.
  • Remove expired or unnecessary invitations instead of leaving them open indefinitely.

Access design

  • Give provider and billing administration only to people who need it.
  • Use separate AI Applications for workloads requiring separate access boundaries.
  • Do not share human accounts or session cookies.
  • Use AI Application API keys for services and CI rather than a personal browser session.
  • Rotate keys and review membership when someone changes role or leaves the team.

Organization versus application configuration

Organization model settings establish shared defaults. AI Application settings can narrow or override provider configuration for one application. A member who can inspect application data does not need access to raw provider credentials; saved credentials are never displayed again.

Continue with API keys and Security and data handling.