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, Connected apps, 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, Connected apps, and Skills. General and Models are visible to every member; the rest are shown only to administrators.

• AI → Models → 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 runs on the model for MINEO's AI helpers, with its key. Off, the organization uses MINEO's models and its own are offered to no one. It can be turned on when the plan allows BYOK; the tabs to set up its credentials, models, groups, deployments and default models appear then. 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 → Regions (administrators only, with Only your own API keys on): the members' AI regions. Enable regions, off by default, turns them on; off, nobody's region applies — everyone may use the models of any region and gets the organization's defaults — and what was set up is kept for when it is turned on again (turning it off asks first). On, it lists, per member region, which regions' models its members may use. To give each region its own models, step by step, see Models by region. There is a row per region any member has (see AI region of each member), and + Region adds another one to prepare it. Its member count — everyone who has the region, first or not — opens them, with a link to the full list in Team → Members. The × removes a region; one with members asks first, and saving takes the region away from them too (their other regions stay). Its May use models of lists first the regions the organization has models in, then the rest (for example, only EU and Global (provider direct); empty: any region). Most MINEO models are Global (provider direct). A region left without a chat model is flagged, and saving asks first. Members without a region use the organization's settings.

• Models → Credentials (administrators only): Store API provider keys for serving your organization's models. Each credential has a key name, the API key (encrypted at rest), its providers (OpenAI, Anthropic, Google: one key may serve several, e.g. a LiteLLM proxy) and optionally a Base URL to override the default endpoint (a gateway or a proxy like LiteLLM). Test connection tries the key with each of its providers before saving. Saving opens the credential's page: its General tab shows, for a LiteLLM key, what the key and its team have spent and their budget, and its Deployments tab lists the models and groups that call with it and for whom. The list's Deployments column warns about a key no deployment uses.

• Models → Models (administrators only): your organization's own models. Each one is a base model of MINEO's catalog (e.g. GPT-5.1, Claude Sonnet) with a display name: pricing, context limits and capabilities are inherited from the base model and stay in sync automatically. The + button asks only for the base model and the name, and then opens the model's page; clicking a model's name in the list opens it too. The list filters All, Active or Retired (retired by its provider, or replaced), and its ⋯ menu has Edit, Test model, Clone — without its deployments: set them on the clone's page — and Delete. The model's page has four tabs:

  • General: the base model, the name and the groups it belongs to.
  • Regions: where it runs, in order, and the model ID it is called with in each region (empty: the base model's). See One model in several regions.
  • Lifecycle: its retirement date (its base model's, kept up to date from LiteLLM's model catalog), its substitute (Replaced by) and the models it replaces (Replaces: picking one there sets this model as its substitute). While it has a substitute, whatever uses the model — its assistants, the default models, the conversations — runs on the substitute, so you can retire a model without editing every assistant; the list counts it as Retired and shows a Replaced by tag. The tab carries a dot when the model retires or is replaced.
  • Deployments: who may use it and with which key, its own deployments and those of its groups. See Deployments.

  A model no deployment gives is offered to no one: the list's Deployments column warns about it. Test model, on its page or in the ⋯ menu, sends a minimal request with the key of one of its deployments; with none, it says so.

• Models → Groups (administrators only): models managed together. A deployment of a group gives every model of it, also the ones added later, so a department's key is set once for its whole catalog. A group's page has its name and models (General) and its Deployments. A model that the key of one of the group's deployments does not serve can't be added: it is shown disabled, with the key and the provider in its tooltip.

• Models → Deployments (administrators only): every deployment of the organization in one table, to search, edit, reorder with the arrows of the Order column or delete several at once. + adds one; picking several projects, groups or users there creates one deployment for each. See Deployments.

• Models → Defaults (administrators only, with Only your own API keys on): the models MINEO uses when nothing else is chosen, in a table with one row per feature and one column for the organization plus, with regions on, one per member region of Models → Regions. A project can set its own default models, ahead of these, in Project settings → AI → Default models (see Projects).

  • 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, code completion and the notebook assistant. 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 and the notebook assistant are disabled with the reason in their tooltip, and code completion stops asking. Their use counts toward the AI cost limits like any conversation's; there is no daily quota of requests.
  • 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): one per member region of Models → Regions. 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 have it as their first region — the one that rules their defaults; 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.

• Models → Effective access (administrators only): pick a project (or Outside a project) and one of its members to see what they get, as their conversations would run: their regions and groups, each model they may use with the key it calls with, the deployment that gives it them and the region and model ID it runs with, the default models, and the models they may not use, grouped by why not.

• Models → Check-up (administrators only, with Only your own API keys on or off): Run check-up looks for what keeps members from the models they need, as their conversations would run, and lists it as Errors (someone is left without a model now) and Warnings (it works, but not as configured):

  • members of a project with no chat model at all;
  • assistants, the organization's and the plan's included, with none of their models available to some members;
  • active scheduled tasks whose creator has no model for their assistant: they would fail on every run;
  • default models that are set but not allowed where they would run (the next one is used instead), and features left with no model that nobody turned off;
  • with Only your own API keys on, deployments whose key is empty or does not serve the model's provider, deployments for someone no longer in the organization or for a group with no members, and deployments of an empty group of models.

  Each one shows the project, the members it affects (their faces; click the count for the full list, each name opening their Effective access) and a Fix link to where it is changed. Nothing is checked until the button is clicked: it goes through every project and kind of member.

• Skills (administrators only): the organization's catalog of skills, seen by every project. Administrators add, edit, clone and delete them; MINEO's own are read-only. A project's own skills are managed in its Workspace → Skills. See Assistant skills.

• 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.

• Connected apps (administrators only): Set up the apps (Gmail, Slack…) that Assistants in every project may use, each with the tools of it they may call. Each member connects their own account. See Connected apps.

Workspace

The Workspace tab provides a central overview of resources shared across the organization: worker images, data sources, Assistants, skills and knowledge bases that administrators have promoted to the organization level. Shared skills are managed in their own project (see Where skills come from). 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.

Skills

Skills a project shares with the organization are available in every project's skill lists and in the Tools menu, with the Organization scope. Other projects can pick them, assign them to their Assistants and clone them; editing stays in the origin project.

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

See Sharing with the organization 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 a license, which says what they can do, and a role, which says where they can manage things. The two are independent.

License (what they can do in the organization's projects; each one is a seat of its own in your plan):

License	What it includes
Viewer	Read-only access. A viewer also talks to Assistants in threads when the plan allows it.
Creator	Works with AI: by default threads, Assistants, skills, knowledge bases, and notebooks and files. Your plan decides exactly what a Creator license includes.
Builder	Everything in the workspace your plan has: also live apps, pipelines, data sources, worker images and development environments.

Threads include whatever modes are enabled for them, such as Work sessions and scheduled tasks. Whatever a license does not include shows a lock in the workspace, with the reason in a tooltip, and MINEO refuses it.

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

An organization always keeps at least one administrator, directly or through a group: MINEO refuses any change that would leave it without one (a new license, a role, removing a member or a group).

Administrators change a user's license from the License column of the members table; the role stays as it is. A license whose seats are all taken can't be picked. The box above the table shows the seats used and available for each license; hover it to see what your plan includes in each one. Sort or filter the table by the Role and License columns.

To change a user's role, open Manage permissions in their row menu. It shows the role you give them, the one their groups give them and the effective one (the highest of both), and, apart, their license.

info

An administrator can have any license: a Creator license administers the project or the organization but does not create, for example, data sources. 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 license to Creator or Builder first.

AI region of each member

With Enable regions on (Models → Regions), administrators see an AI regions column in the members table: one or several regions — any country, the European Union or Global (provider direct), searched by name — 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 Models → Regions, and its default models in Models → Defaults, 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, choosing the license they join with (Builder unless you pick another), their role (Member or Administrator; a Viewer license is always the viewer role) and, optionally, the groups they join (one or several):

• 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 how many Builder, Creator and Viewer licenses your organization can have. To add more users with a license whose seats are taken, 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 licenses (Builder/Creator/Viewer) remain unchanged: a group gives a role, never a license. 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. A project that sets some of its own shows how many under Configure (for example, 2 custom permissions).

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 connected apps, or moving an organization one into the project. Existing project integrations and connected apps keep working. See Integrations.

• Create skills: restricting it prevents project members, administrators included, from creating or cloning skills of their own in Workspace → Skills. The project's existing skills keep working and can still be edited. See Where skills come from.

• Create assistants: restricting it prevents project members, administrators included, from creating or cloning assistants in Workspace → Assistants (or from an assistant picker's New Assistant). The project's existing assistants keep working and can still be edited. Allowed by default.

• Create knowledge bases: restricting it prevents project members, administrators included, from creating or cloning knowledge bases in Workspace → Knowledge bases. The project's existing knowledge bases keep working and can still be edited. Allowed by default. See Knowledge bases.

• Use the project's files: restricting it takes the project's files out of use, for everyone in the project:

  • The Explorer, Live Apps, Dev environments and Pipelines are off, whatever their module setting. Nobody reads or writes the project's files, through MINEO or its API.
  • Assistants work only on the Gallery of whoever uses them: choose User's Gallery as their working directory. An assistant already set to the project's files has no file tools in this project and says so when asked for a file.
  • Work sessions run only on the user's Gallery.

  Use it for projects that only chat with assistants, such as a department's: each person keeps their files in their own Gallery. Allowed by default.

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 four 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

AI adoption

See how much your organization uses AI, who uses it and what it costs: active users, the adoption funnel, the features and assistants used, adoption by team and who keeps using it. Only administrators see this sub-section. See AI Adoption.

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.