Skip to main content
Osintly separates Personal workspaces from organization workspaces. Organization permissions are checked for every protected action, not only when an interface button is visible.

​
Workspace modes

Personal workspace

One user owns their plan, credits, searches, API keys, and billing context.

Organization workspace

Members use a shared plan, credits, history, API account, and organization billing.

​
Roles

* Admins can remove members but cannot remove the owner or another admin.

​
Billing and credit behavior

When a member launches a full search in an organization workspace, one credit is reserved from the organization’s shared allowance. The same organization subscription determines plan access for all members of that workspace.
  • Personal subscriptions and credits are never used automatically in the organization.
  • An organization subscription does not upgrade a member’s Personal workspace.
  • A member in several organizations gets a separate role and organization allowance in each one.
  • The owner is the only role that can manage organization billing.
Tool lookup overrides also use the organization allowance when the organization is active. See Tool usage limits.

​
Access behavior

Organization history is visible to all organization members and identifies the member who created each entry. Personal history stays private to its owner.
Selecting an organization does not expose Personal data, another organization, or legacy Team data. A workspace preference is rechecked server-side and is never treated as authorization by itself.
Monitoring permissions are scoped to the selected workspace. Owners and admins can manage organization notification channels; see Monitoring & Alerts.

​
Operational recommendations

  • Keep the owner role limited to people responsible for billing and lifecycle actions.
  • Use the workspace switcher deliberately before launching a search or creating an API key.
  • Review members, pending invitations, usage, and API keys regularly.