Organizations

An organization is a workspace that groups together:

• Projects: All your team's notebooks, live apps, pipelines, and files
• Users: Team members with specific roles and permissions
• Subscription: Shared resources (CPU/GPU hours, storage) and billing

Organizations are ideal for:

• Companies managing multiple client projects
• Teams collaborating across different departments
• Managing billing and resources in one place

Users can belong to multiple organizations and switch between them as needed.

info

Every member can open the organization page and browse its tabs. Changing organization settings requires the Administrator role; the Integrations tab and the administrator-only AI sub-tabs (Limits, Compaction, MCP servers, Skills) are shown only to administrators.

When you have no active project in an organization (for example, an administrator who is not a viewer of any project), MINEO opens the organization page directly and the sidebar lists its tabs.

General

The General tab contains two sub-sections for managing your organization:

General Information

Configure the basic details of your organization:

• Name: The display name for your organization. This is visible to all members and appears throughout the platform.
• Description: A brief explanation of your organization's purpose or scope. Helps team members understand the organization's context.
• Avatar/Logo: Upload an image to visually identify your organization (optional).

These details help personalize your workspace and make it easier for team members to identify and understand the organization's purpose.

Custom Domains

Configure how your organization and Live Apps are accessed publicly. MINEO offers two options:

• Slug: Quick setup using MINEO's domain (e.g., b.mineo.app/your-slug/live_app/app-name)

  • Perfect for internal team use and getting started
  • Free and easy to configure

• Custom Domain (Pro plans): Use your own domain (e.g., apps.yourcompany.com/live_app/app-name)

  • Professional branding for client-facing applications
  • Requires DNS configuration
  • Available on select paid plans

tip

For detailed information about configuring slugs and custom domains, including DNS setup, see Slug and Custom Domains.

AI

The AI tab groups the AI settings shared across the organization in sub-tabs: General, Limits, Models, Work, MCP servers, and Skills. General and Models are visible to every member; the rest are shown only to administrators.

• General → Only your own API keys (BYOK): no request reaches a provider on MINEO's keys. Assistants, Work, voice and MINEO's helpers only use the organization's models: an assistant whose model is a platform one switches to one of its own allowed models, or stops answering until it has one. The notebook assistant is turned off. It can be turned on only when the plan allows BYOK and the organization has a chat model of its own. Turning it on clears the default models that are MINEO's, the organization's and each region's. For the whole setup, step by step, see Use only your own API keys. Administrators only.

• General → Chat disclaimer: A short notice shown permanently below the chat input in threads (including shared threads), for every project in the organization (e.g. "AI can make mistakes. Check important information."). Toggle Show chat disclaimer to enable it, then write the message. It supports Markdown, so you can include links to your usage policy. The disclaimer is disabled by default.

• Work (administrators only): the Work mode switch lets members start Work sessions, long-running agents that run in their own workspace. It is on by default when your plan includes Work mode; if the plan does not, the switch is shown off and cannot be changed. Turning it off stops members from starting, restarting or sending prompts to Work sessions; sessions already running can still be viewed and stopped. Max concurrent Work sessions sets how many sessions can run at the same time across the organization: your plan's ceiling is always shown and you can lower it, never raise it (leave it empty to use the plan's). Max concurrent Work sessions per user does the same for each person's sessions. Lowering either does not stop running sessions; it applies when a session starts. Maximum turn duration caps how long a single agent turn may run before the session is stopped as a safety measure; like the sessions limit, it can be lowered below the plan's ceiling but not raised.

• General → Web search domain restrictions (administrators only): Control which websites Assistants in this organization can search. Two independent lists are available:

  • Allowed domains — when set, all web searches across every Assistant are restricted to these domains only.
  • Blocked domains — domains excluded from all search results, regardless of the query.

  Enter bare domain names (e.g. wikipedia.org) — no scheme (https://), no path. Leave both lists empty to impose no organization-wide restriction. These settings override per-assistant domain configuration; the assistant form displays the active lists as read-only when an organization-level restriction is in place. See Web search for the per-assistant configuration.

• Limits (administrators only): USD cost limits per user (daily, weekly, monthly) and for the whole organization (monthly), with per-user, per-group and per-project overrides and an extra usage wallet per user. Warning at 80%, block at 100%. See AI Cost Limits.

• Models → Credentials (administrators only): Store API provider keys (OpenAI, Anthropic, Google, Azure OpenAI) for serving custom models. Each credential requires a provider, a key name, the API key (encrypted at rest), and optionally a Base URL to override the default endpoint (required for Azure OpenAI; also useful for self-hosted gateways or proxies like LiteLLM). You can test the connection before saving. Credentials are the foundation for BYOK models — you must add a credential before creating a model.

• Models → Models (administrators only): Create Bring Your Own Key (BYOK) models using your organization's credentials. Each model links a credential to a base model from your plan (e.g. GPT-4o, Claude Sonnet). Pricing, context limits, and capabilities are inherited from the base model and stay in sync automatically. The + button asks only for the credential, the base model and a display name, and then opens the model's own page; clicking a model's name in the list opens it too. Its General tab also lets you override the model ID sent to the provider and choose a hosting region (useful for Azure OpenAI regional deployments). Once created, these models are available to the organization's assistants alongside the plan's global models.

  • Projects tab of the model's page: a chat model is usable in All projects by default, including the ones created later. Turn it off and move the projects that may use it to the right-hand list (Projects with this model); the others don't list it in their model pickers and can't select it for their assistants. Nothing changes until you press Save. Image and voice models are always available to every project. The list's Available in column shows the result.
  • Members tab of the model's page: a chat model is usable by All members by default, including the ones who join later. Turn it off and move to the right-hand lists the users and the groups that may use it: a member has it when they are one of those users or belong to one of those groups. Projects and members apply together — the model is used only in its projects and only by its members. For everyone else it is not offered in the chat's model picker, and an assistant that runs on it uses the next of its models they can use (or stops answering for them if it has none). Whoever edits an assistant can only add the models they may use themselves; an administrator can still pick any model as a default model of the organization. Before saving, MINEO tells you how many members lose the model and who. The list's Available in column shows the number of users and groups. Someone who leaves the organization is removed from its models.
  • Taking a model away from a project never changes its assistants. Before saving, MINEO lists the assistants that use it there and what happens to each one: it keeps its own model, it switches to another of its allowed models, or it has no model left and stops answering in that project until one is assigned. Assistants shared with the whole organization are checked in every project that loses the model.

• Models → Default models (administrators only): the models MINEO uses when nothing else is chosen, in a table with one row per feature and one column for the organization plus one per member region. To give each region its own models, step by step, see Models by region.

  • May use models of: the regions of the models that may be used. In the Organization column it applies to everyone and to what administrators configure (for example, only EU and Global (provider direct)); saving lists first the assistants that switch model or are left without one, as Only your own API keys does. In a region's column it can only be narrower. Empty means any region. Most MINEO models are Global (provider direct).
  • Compaction model: writes the summary when a thread is compacted; empty means the thread's own model. See Context window and compaction.
  • Model for MINEO's AI helpers: used by MINEO's helpers — optimizing instructions, generating starters, form fields and assistant setups, skills, Dockerfiles and code completion. Empty means MINEO's system model; with Only your own API keys on, those helpers need one. Off, or without a model: their magic-wand buttons are disabled with the reason in their tooltip, and code completion stops asking.
  • Image generation model: used by assistants that generate images without a model of their own. Empty means the plan's first image model. Off, no assistant generates images for those members — not even one with an image model of its own.
  • Dictation model and Reading aloud model: OpenAI models created under Models → Models from a speech base model, or empty for MINEO's. With Only your own API keys on, one without a model of its own stays off and its button is disabled, with the reason in its tooltip.
  • The switch next to the helpers, image, dictation and reading aloud models turns that feature on or off.
  • Member regions (the columns): a region with members (see AI region of each member) gets its own column, and + Region adds another one to prepare it. Each of its cells overrides the organization's for its members: an empty cell says what it inherits, or that the feature is off. A region can turn a feature off for its members, or on with a model of its own where the organization has it off — saving asks for that model. Its header shows how many members it has — click the number to see them, with a link to the full list in Team → Members — and warns when they are left without a chat model; saving asks first in that case. Members without a region use the organization's column.
  • Each save that changes this table is recorded in Activity → Events (User change default models), with every column it changed as it was and as it is.
  • A default model not allowed where it would run (for example, one limited to other projects or not of the member's regions) is skipped: MINEO falls back to the next choice — the region's, then the organization's, then MINEO's.

• Skills (administrators only): Create and manage reusable prompt fragments shared by Assistants in every project in the organization. Administrators can add, edit, clone, categorize, and delete organization skills. Members and viewers can browse them, and users with permission to edit an Assistant can select them, but only organization administrators can change the shared catalog. Global MINEO skills remain read-only. See Assistant skills for loading modes, token usage, and selection behavior.

• MCP servers (administrators only): Create and manage remote tool servers shared with Assistants in every project in the organization. Open AI → MCP servers to configure the endpoint and authentication, test the connection, and synchronize its tools. The organization catalog contains only organization-scoped servers; project settings show both project servers and inherited organization servers. See MCP servers for scopes, permissions, and tool configuration.

Workspace

The Workspace tab provides a central overview of resources shared across the organization: worker images, data sources, and Assistants that administrators have promoted to the organization level. Each sub-tab lists the shared resources with their origin project; members and viewers can browse them, and administrators can stop sharing from the ... menu.

Worker images

Worker images shared at the organization level are available in every project's worker image selector, marked with an Organization badge. Administrators can:

• Promote: From any project's worker image list (or the image's Permissions tab), share it across all projects
• Demote: From the organization's Workspace tab (or the image's Permissions tab), stop sharing it. Resources in other projects that used it are unlinked and fall back to their default image; the image's own project is unaffected

See Worker Images for details on creating and managing worker images.

Data sources

Data sources shared at the organization level are available in every project's Data Sources list and selectors, marked with an Organization badge. Other projects can query them, test the connection, and scan tables; editing, cloning, and deleting stay in the origin project.

• Promote: From the data source's ... menu in its project, select Visibility → Organization.
• Demote: From the organization's Workspace → Data Sources tab, open the ... menu and select Visibility → Project (the same menu offers Go to project). MINEO asks for confirmation. The same option is available from the project menu.

See Organization-level data sources for details.

Assistants

Assistants shared at the organization level are available in every project's Assistants list and thread picker, marked with an Organization badge. Other projects can chat with them; editing, cloning, deleting, and setting as default stay in the origin project.

• Promote: From the Assistant's ... menu in its project, select Visibility → Organization.
• Demote: From the organization's Workspace → Assistants tab, open the ... menu and select Visibility → Project (the same menu offers Go to project). MINEO asks for confirmation. The same option is available from the project menu.

See Organization-level Assistants for details.

Integrations

The Integrations tab (administrators only) holds connections shared by every project in the organization: Slack, Email, SSH keys, Google Drive, and SharePoint/OneDrive. They appear in each project's Settings → Integrations with an Organization badge, in Assistant connection selectors, and in notification rules, grouped under Organization. Only organization administrators edit or delete them; project administrators who also administer the organization can move an integration between the project and organization scopes from the project's integration form.

One SSH key is allowed per organization. Git operations use the project's own key and fall back to the organization's key when the project has none.

Use Projects → Default permissions (or Configure for a single project) to allow or restrict Create integrations for project administrators. Existing project integrations keep working when creation is restricted.

Members

The Members tab helps you manage user access to your organization. It contains two sub-sections:

Members

Add and manage users who have access to your organization. Each user has two independent role dimensions:

Content Access Role (what they can do with project resources):

• Viewer: Can only view resources like notebooks and files (read-only access)
• Editor: Can edit notebooks and files based on project permissions

Organization Role (their organization permissions):

• Member: Can access the organization but cannot change organization settings
• Administrator: Has full control over organization settings, user management, and billing

info

A user can be an "Editor + Member" (can edit content but not manage the organization) or an "Editor + Administrator". The Viewer license prevails over everything else: a viewer is always read-only and never gets member or administrator permissions, in the organization or in its projects, even if a group they belong to has that role. To give a viewer more permissions, change their content access role to Editor first.

AI region of each member

Administrators see an AI regions column in the members table: one or several of US, EU, China and Global (provider direct), or none. A member with several may use the models of all of them; the order matters — the first one decides their default models and is the one an assistant prefers (see Models by region). Pick them in the order you want; to reorder, remove a region and pick it again. Filter the column by a region, or select several members and use Assign AI regions to set them for all at once; with no region picked, its button reads Remove their regions and clears them. What a region lets them use is set in its column of Models → Default models, and administrators are restricted like everyone else. Each change is recorded in Activity → Events with who made it and the previous and new regions. A member who leaves the organization loses their regions.

The Online column shows which members currently have MINEO open in their browser (green dot). It reflects an open browser tab, not a running worker or notebook, and refreshes when you reload the page. Sort by the column to bring online members to the top.

You can add users in two ways:

• Add Existing Users: Bring existing MINEO users into your organization
• Invite New Users: Send email invitations to users not yet on MINEO

Adding or inviting someone who is already in the organization never changes their role or their groups: they only receive the email again. Change roles from the Members table and groups from the Groups tab.

caution

Your plan sets limits on viewers and editors. To add more users, you may need to upgrade your plan.

Invitations

Manage pending email invitations sent to users who haven't joined MINEO yet. In this tab you can:

• View all pending invitations
• Resend invitations if needed
• Cancel invitations before they are accepted
• Assign roles and permissions to invited users before they even log in

Invitation emails are sent in the background, so inviting many people at once does not keep you waiting. If an email cannot be delivered, MINEO tries again a few times over the next ten minutes; an invitation whose email never got through is shown as Errored, and resending it puts it back to Pending.

tip

Invited users are pre-created in MINEO, allowing administrators to configure their access and permissions in advance.

Groups

Groups allow you to manage multiple users as a single unit, making it easier to assign roles and permissions at scale.

What are Groups?

A group is a collection of users that share the same organization role. Instead of configuring each user individually, you can:

• Create a group with specific permissions
• Add multiple users to that group
• All group members automatically inherit the group's organization role

How Groups Work

Organization Role Inheritance

• Each group has an organization role (Member or Administrator)
• Users in the group inherit this role for organization-level permissions
• Individual content access roles (Viewer/Editor) remain unchanged. A viewer stays a viewer even inside an Administrator group: the license prevails over the group role

Multiple Group Membership

• Users can belong to multiple groups simultaneously
• When a user belongs to multiple groups with different roles, the least restrictive role applies
• Example: If a user is in "Developers" (Member) and "Team Leads" (Administrator), they will have Administrator permissions

Common Use Cases

• Department-based access: Create groups like "Engineering", "Sales", "Support" with appropriate permissions
• Client segregation: Separate groups for different client teams with limited access
• Project teams: Temporary groups for specific projects that can be easily dissolved
• Role-based management: "Administrators", "Managers", "Contributors" with different permission levels

Projects

The Projects tab allows administrators to view and manage all projects belonging to the organization.

What are Projects?

Projects are workspaces where your team creates and manages computational resources like:

• Notebooks: Interactive Jupyter notebooks for data analysis and development
• Live Apps: Published applications (Streamlit, Gradio, etc.) accessible to users
• Pipelines: Automated workflows and scheduled tasks
• Files and Datasets: Shared storage for project resources

Managing Projects

In this tab you can:

• View all projects: See all projects associated with your organization
• Create new projects: Add projects up to your plan's limit
• Monitor project status: Check which projects are active and their resource usage
• Access project settings: Navigate directly to individual project configurations
• Mark favorites: the Favorites column stars a project; the same star button in the toolbar filters the table to favorites only. Favorites are personal, not shared with other members. My profile → Organizations has the same column for organizations.

Configure project permissions

Organization administrators can control which projects may configure specific project-owned resources:

1. Open Organization settings → Projects.
2. Select Default permissions.
3. Choose Allow or Restrict for each default permission.
4. Select Save.

The organization default applies to every project that inherits it. Changing the default therefore affects inheriting projects immediately, while explicit project overrides remain unchanged.

For a single project, select Configure in its Permissions column. The same action is also available from the row menu. Both open a project-focused editor with Inherit / Allow / Restrict for each policy; the toolbar action remains available for organization defaults.

Available policies:

• Create MCP servers: restricting it prevents project administrators from creating project-scoped MCP servers or moving an organization server into the project. Existing project servers remain linked, visible, editable, and usable. Organization-scoped server creation is not affected.
• Create integrations: restricting it prevents project administrators from creating project-scoped integrations or moving an organization integration into the project. Existing project integrations keep working. See Integrations.

info

Effective access follows three checks: the subscription plan must include MCP, the project must be allowed by the organization policy, and the user must be a project administrator.

caution

The number of available project slots is determined by your purchased subscription. To create more projects, you may need to upgrade your plan.

Project Permissions vs Organization Permissions

Important: Organization permissions and project permissions are managed separately:

• Organization permissions (configured in the Members/Groups tabs): Control who can manage the organization itself
• Project permissions (configured within each project): Control who can access and edit resources within that specific project

This separation provides flexibility to:

• Give someone organization admin access without access to all projects
• Grant project-specific access to external collaborators without organization membership
• Create different permission structures for different projects within the same organization

tip

For detailed information about project configuration and permissions, see the Projects documentation.

Activity

The Activity tab allows administrators to monitor organizational events and resource usage. It contains three sub-sections:

Stats

Monitor your organization's resource consumption with detailed metrics on compute and storage usage.

Period selection (CPU/GPU and AI)

• View by: aggregate consumption by Day, Week or Month. The chart always spans every bucket returned (last 30 days, 26 weeks or 12 months)
• Detail of: the range the KPI cards and the detail tables summarise (e.g. last 7 days, last 4 weeks, last month)
• Quotas (CPU/GPU hours per user and month, AI monthly budget) are defined per month, so their percentages and progress bars only appear on a single-month range

CPU/GPU Usage

• View total CPU and GPU hours consumed in the selected range
• Compare usage against your plan's available hours
• See number of active sessions using compute resources
• Breakdown per user and per project, filterable by Project and User
• Visual indicators showing usage percentage relative to your quota

Storage Usage

• Track total storage consumption across the organization
• Monitor storage usage per project
• Compare against your plan's storage limit
• Worker images: registry space taken by the worker images, with a Per worker image detail table (image, project, latest tag, number of tags, space). Only the most recent tag of every image counts towards the space — older tags share most of their layers with it, and the tag count tells you how much history has piled up behind it
• Identify which users or projects are consuming most storage space

AI Usage

• View total AI cost (USD) consumed in the selected range
• Compare cost against your plan's monthly AI budget
• Track total requests and tool calls made to AI models
• Breakdown of input and output tokens per bucket
• Breakdown per user and per project of cost, requests, and token usage
• Filter by Project, Provider, Model, and User; administrators can jump to limits via Manage limits

note

The Storage section queries the storage backend once per project, so it is only loaded the first time you open its tab. The CPU/GPU and AI sections never wait for it.

Usage

Track how organization members interact with different project resources:

• Notebooks: Monitor access and usage patterns for Jupyter notebooks
• Live Apps: See which published applications (Streamlit, Gradio, etc.) are being accessed
• Pipelines: View activity on automated workflows and scheduled tasks

This information helps administrators:

• Monitor team engagement with different resources
• Identify most-used applications and notebooks
• Optimize resource allocation based on actual usage patterns
• Make informed decisions about infrastructure needs

Events

View a chronological timeline of important organizational activities with powerful filtering and export capabilities.

Event types tracked:

• User additions and removals
• Project creation and deletion
• Permission changes on resources
• Organization membership updates
• Configuration updates
• Worker session terminated
• Other administrative actions

Filtering options:

• Event type: Filter by specific event categories
• Project: Filter events by project
• User: Filter events by user who performed the action
• Date range: Select a specific time period with preset options (Today, Last 7 Days, Last 30 Days, etc.)
• Message search: Search within event messages

Event details: Each event record includes:

• Date and time of the action
• Event type with color-coded tags
• User who performed the action
• Associated project (if applicable)
• Resource affected
• IP address of the request
• Additional properties and messages

Export: Download the complete event log as an Excel file for external analysis, reporting, or compliance purposes.

This audit trail helps administrators maintain oversight of organizational changes, track who did what and when, and meet compliance requirements.

Plan

View and manage your organization's subscription plan and billing.

What you'll see:

• Detailed breakdown of your current plan features (users, storage, computing resources, etc.)
• Comparison table with available upgrade options
• Subscription renewal information and billing alerts

What you can do:

• Upgrade to a higher plan
• Manage billing through the customer portal (payment methods, billing history)
• Cancel or modify your subscription

tip

For detailed pricing information, visit the MINEO Pricing page.

Advanced

The Advanced tab contains critical organization management options.

Initialize

Copy the resources of a base project into every project of the organization. Only organization administrators who are also administrators of the base project can run it.

1. Select the Base project.
2. In the tree, uncheck what you do not want to apply (everything is checked by default):
   • Create a project for each member without one: every member who does not administer any project gets a new project named after their username.
   • Assistants, Dev environments and Data sources: check the whole group or only some of its items.
   • Files and folders: copies the base project's file tree.
3. Click Apply and confirm.

A dialog shows the progress and, when it finishes, how many projects were created and how many resources were copied or skipped. The initialization applies to every project, including the ones it creates. Resources that already exist in a project (same name) are skipped, so running it again never duplicates or overwrites anything. Copied assistants use the copied data source of their project. The run is also logged in the Activity tab.

warning

The Apply button stays disabled while something cannot be copied correctly: an assistant whose data source is not selected, or that uses a team knowledge base or MCP server not shared with the organization; a dev environment using an image not shared with the organization; or a working directory or SQLite data source without Files and folders selected.

info

Personal memory bases belong to their user, not to a project: they never block the initialization and they are not carried over to the copied assistants.

Delete Organization

Permanently remove the organization and all its associated data. As with deleting a project, the dialog asks you to type the organization name to confirm. The deletion includes:

• All projects and their resources (notebooks, files, pipelines, live apps)
• User memberships and groups
• Configuration and settings
• Activity history

caution

This action is irreversible. Once deleted, the organization and all its data cannot be recovered. Make sure to back up any important data before proceeding.