> ## Documentation Index > Fetch the complete documentation index at: https://docs.osint.ly/llms.txt > Use this file to discover all available pages before exploring further. # Organizations & workspaces > Create an organization, switch workspaces, and understand shared searches, credits, and usage. Dates and clock times shown in organization activity, shared history, usage, and billing views are displayed in **UTC**. An organization is a paid, shared Osintly workspace for a company, agency, or research group. It has its own members, plan, credit allowance, search history, API account, and billing. Your **Personal** workspace always remains separate. Organizations are the current shared-workspace model. Legacy Team projects remain separate until their owner [transfers the Team](/collaboration/legacy-team-transition); a search cannot belong to both a Team and an organization at the same time. *** ## Personal and organization workspaces Use the workspace menu in the sidebar to switch between **Personal** and any organization you belong to. The selected workspace determines which plan, credits, history, and API account are used for your next action. | In Personal | In an organization | | - | - | | Your individual plan and credit balance apply | The organization's plan and shared credit allowance apply | | History contains your personal searches | History contains searches made by organization members | | API keys and usage belong to your account | API keys and usage belong to the organization | | Your personal billing is managed in Settings | Organization billing is managed by its owner | Switching workspace does not move existing searches, credits, subscriptions, or API keys. Members can belong to more than one organization, and each membership is independent. *** ## Create an organization In the sidebar, open the workspace switcher and select **Create organization**. Select **Pro** or **Ultimate**, then choose the number of paid seats. The owner counts as one seat. Osintly shows the recurring amount before payment. The organization becomes available after payment is confirmed. Select the organization, open **Members**, and send email invitations to the people who need access. Self-service organizations support from 1 to 25 paid seats. For larger deployments or custom requirements, contact [sales](https://osint.ly/support/sales). *** ## Shared searches and history Searches run while an organization is selected are stored in that organization’s history. All members can view them, and the history identifies the member who launched each search. * Members can delete their own organization searches. * Owners and admins can delete searches created by any organization member. * Searches in Personal, a legacy Team, or another organization are not shown in the active organization history. * Saved tool results follow the selected workspace too, so members can revisit the organization’s shared tool history. Active organizations can create shared [investigations](/collaboration/investigation-projects) for searches, files, and notes. Legacy Solo and Team projects do not move when you simply switch workspaces. Before the transition deadline, the Team owner can [transfer the entire Team](/collaboration/legacy-team-transition) to an eligible organization; older Solo projects remain export-only. *** ## Shared credits and usage The organization has one shared search allowance per billing period: | Organization plan | Included credits per paid seat | | - | -: | | Pro | 100 | | Ultimate | 200 | The allowance is calculated from the number of paid seats. For example, a three-seat Pro organization has 300 shared credits for the billing period. Credits are not split into individual member wallets: one member may use more of the shared allowance than another. Before a full search starts, Osintly reserves one organization credit. It settles the credit only after the search is created and releases the reservation if the launch fails, which prevents concurrent members from overspending the shared allowance. Open **Organization → Usage** to review shared consumption and limits. Open **Organization → Activity** to inspect and export the audit trail of member actions. See [Credits explained](/guides/credits-explained) and [Tool usage limits](/tools-reference/usage-limits) for spending and volume rules. *** ## Organization console The selected organization has separate pages for **Overview**, **Members**, **Permissions**, **Usage**, **Activity**, **Credits**, **Billing**, **Settings**, and **Security → SSO**. Available pages and actions depend on your role. The overview summarizes the plan, credit use, members, and recent searches. See [Organization activity](/collaboration/organization-activity) for audit filters and exports and [Members & permissions](/collaboration/team-collaboration) for role controls. *** ## Organization billing The owner uses **Organization → Billing** to change the Pro/Ultimate plan, manage paid seats, review payment details, and open invoices. The page shows whether a requested change is scheduled, processing, or waiting for payment. A scheduled change can be undone before it takes effect; an open invoice may need payment to restore access. Cancellation can be reversed before the end of the paid period. The organization app subscription and its API subscription have separate billing views. *** ## Access when billing changes An organization must have an active subscription for members to use its product workspace. If the subscription becomes inactive, members cannot continue to use that organization’s paid workspace. The owner can still use organization billing to resolve the subscription; Personal workspaces and other organizations are unaffected. Changing or cancelling an organization subscription does not alter members’ personal subscriptions or data. *** ## Next steps Invite people and assign the right role. Use organization-scoped API keys, usage, and billing.