Projects
A project is an isolated workspace where teams develop and deploy their work. Each project contains:
- Live Apps: Published applications (Streamlit, Gradio) accessible to users
- Pipelines: Automated workflows and scheduled tasks
- Files: Shared storage for datasets and resources
- Data Sources: Connections to databases, APIs, and external data systems
- Dev Environments: Configurable execution environments for development and testing
- Threads: AI-powered conversation threads for exploring and analyzing data
- Assistants: Custom AI assistants configured for your project's needs
- Notebooks: Interactive development environments for data analysis and coding
- Independent configuration: Each project has its own settings, permissions, and resources
Projects can belong to organizations or exist independently, providing flexibility in how teams structure their work.
Only project administrators can configure projects. Members can access and use project resources but cannot modify settings.
General
The General tab contains multiple sub-sections for configuring your project:
Project
| Setting | Description |
|---|---|
| Name | Project display name visible to all members. |
| Description | Brief explanation of the project's purpose. |
| Avatar/Logo | Optional image to visually identify the project. |
Modules
Choose who sees each of the project's sidebar sections, and in which order. Every module has three settings:
| Setting | Effect |
|---|---|
| Everyone | Visible to every project member. Default. |
| Admins | Visible only to project administrators. Members and viewers don't see the section in the sidebar. Creating items is still allowed. Useful, for example, to keep the file Explorer for administrators while members only use Assistants that read those files. |
| Off | Hidden from everyone, and creating new items is blocked by the backend. |
A module can only be restricted relative to the organization's pricing plan, never enabled beyond it.
| Module | Effect when set to Off |
|---|---|
| Home | Project landing page hidden. |
| Explorer | File browser hidden. |
| Threads | AI conversation threads hidden; new threads blocked. |
| Assistants | Custom assistants hidden; new assistants blocked. |
| Worker images | Worker images hidden; new images blocked. |
| Dev environments | Dev environments hidden; new ones blocked. |
| Live apps | Live apps hidden; new apps blocked. |
| Data sources | Data sources hidden; new connections blocked. |
| Pipelines | Pipelines hidden; new pipelines blocked. |
| Observability | Scanners and issues hidden; new scanners blocked. |
| Notifications | Notification rules hidden; new rules blocked. |
Reorder — use the up/down arrows on each row to set the order sections appear in the sidebar, within their level (the top-level entries, and the modules grouped under Workspace). Settings can be reordered but never restricted.
The Workspace row has a master control that applies one setting to all its modules at once.
Notes:
- A module not included in your pricing plan appears locked and cannot be enabled here.
- At least one module must stay on Everyone, so members always see something; Admins and Off don't count.
- Changes are saved automatically; the sidebar updates immediately.
- When the section a project would normally open on is disabled, it lands on the first enabled entry in your sidebar order.
Only project administrators can change modules.
Explorer
Set the default view for browsing project resources:
| View | Description |
|---|---|
| Icons View | Visual grid layout with thumbnails. |
| List View | Compact table layout with details. |
Notebook
Configure global settings for all notebooks in the project. These settings apply to all notebooks but can be overridden individually.
Formatting options:
| Setting | Default | Examples |
|---|---|---|
| Integer format | 0,0 (1000 → "1,000") | 0 (no separator), 0a (abbreviated: "1k") |
| Float format | 0,0.00 (1234.5 → "1,234.50") | 0.000, 0,0.0000, $0,0.00 |
| Date format | System default | DD-MM-YYYY, MM/DD/YYYY, YYYY-MM-DD |
Numeric formats use Numeral.js syntax. Date formats use Day.js syntax.
Visual style options:
| Category | What it controls |
|---|---|
| General | Font family and general appearance. |
| Title | Block title styling (font color, weight, size, background). |
| Spacing | Padding around blocks. |
| Border | Block border style, width, color, and radius. |
| Shadow | Drop shadow effects for blocks. |
| Block Background | Background colors, gradients, or images for individual blocks. |
| Notebook Background | Background styling for the entire notebook canvas. |
| Grid | Layout grid configuration (columns, margins, responsive behavior). |
| Topbar | Notebook toolbar appearance. |
Resources
Add custom resources loaded automatically in all project notebooks:
| Type | Description |
|---|---|
| JavaScript files | Custom scripts for enhanced functionality. |
| CSS files | Custom styles for notebook appearance. |
| Raw resources | Other files accessible to notebooks. |
Environment
Define environment variables accessible across all project workers:
- Available in notebooks, live apps, and pipelines
- Set as standard environment variables in execution environments
- Useful for API keys, configuration, and secrets management
Environment variables are visible to all project members. Do not store sensitive credentials here.
AI
Open Project settings → AI → MCP servers to manage the remote tools available to the project's Assistants. The catalog shows:
- servers owned by the current project, marked Project · project name;
- servers shared by the parent organization, marked Organization.
Project administrators can create, edit, synchronize, and delete project-scoped servers. Organization administrators manage organization-scoped servers; when you have that role, the page provides an Organization settings shortcut. Moving a server between scopes requires both roles.
An organization administrator can restrict project-scoped MCP server creation from Organization settings → Projects. Use Default permissions in the toolbar for organization defaults, or Configure in a project's Permissions column to configure only that project. The individual editor shows Inherit / Allow / Restrict for every policy and is also available from the row menu. Inherit follows future changes to the organization default; explicit overrides do not. When effectively restricted, the add action displays a lock and organization-to-project scope changes are unavailable. Existing servers remain available and can still be edited, synchronized, linked, and used.
See MCP servers for setup, scope changes, authentication, and per-Assistant tool permissions.
Workers
A worker is the computational environment where your code executes. Every time you run a notebook, launch a live app, or execute a pipeline, MINEO creates a worker (a container) with the specified resources and software stack.
Configure the default worker settings for your project:
Worker Image
- Select the default worker image for the project
- Contains the software stack (Python version, libraries, tools)
- Can be overridden per notebook, live app, or pipeline
Worker environment
- Choose default computational resources for execution
- Specify CPU, RAM, and GPU allocations
- Different templates available based on your plan
These defaults apply to all new notebooks, live apps, and pipelines created in the project, but can be customized individually.
Members
Manage user access and permissions for this project.
Project roles
Each user has one of two roles:
| Role | Permissions |
|---|---|
| Member | Access and use project resources. Create and edit own content based on permissions. Cannot modify project settings or manage users. |
| Administrator | Full access to project configuration, settings, members, and all resources. |
Organization vs Project Roles
Important: Organization roles and project roles are independent. A user can be:
- Organization Administrator but Project Member (can manage org settings, but not this specific project)
- Organization Member but Project Administrator (can manage this project, but not the organization)
This separation provides flexibility in permission management.
Managing Members
Administrators can:
- Add existing organization members to the project
- Assign or change user roles (Member/Administrator)
- Remove users from the project
Users must first be members of the parent organization before they can be added to a project.
Groups
Add organization groups to the project to manage multiple users simultaneously.
How Groups Work in Projects
When you add a group to a project:
- All group members automatically gain access to the project
- Each group is assigned a project role (Member or Administrator)
- All group members inherit that role for this specific project
Available Groups
Only groups created in the parent organization can be added to projects. Create groups at the organization level first, then add them to projects as needed.
Role Precedence
When a user belongs to multiple groups with different roles:
- Administrator role takes precedence over Member role
- If a user is a Member individually but belongs to a group with Administrator role, they will have Administrator permissions
- The least restrictive role always applies
Example:
- User is added as Project Member
- User belongs to "DevOps Team" group with Administrator role
- Result: User has Administrator permissions in the project
Integrations
Connect your project with external services to enhance functionality and streamline workflows.
Integrations belong to the project or to its organization. Organization integrations show Organization in the Scope column and are read-only here unless you administer the organization; project administrators manage project ones. If you administer both, the form offers a Scope selector and you can move an integration between scopes — moving one to the project disconnects Assistants and deletes notification rules in other projects that used it (MINEO shows the count and asks for confirmation). Only one SSH key is allowed per scope.
Organization administrators can restrict project-level creation with the Create integrations policy. When it is off for a project, the "+" button shows a lock and Your organization restricts project integration creation; existing integrations keep working.
| Integration | Setup | Use cases |
|---|---|---|
| Slack | Create a Slack Webhook, configure the URL, and select which notifications to send. | Pipeline alerts, error notifications, activity updates. |
Add email addresses (comma or line-separated) and select notifications. Sent from mineo@mineo.app — whitelist to avoid spam filters. | Pipeline execution alerts, error notifications, team updates. | |
| SSH Keys | Generate or import SSH key pairs. Add public keys to external services. | Private Git repos, remote server access, secure file transfers. |
| Sentry | Coming soon — not available yet. | Real-time error tracking, performance monitoring, debugging. |
Activity
Monitor project consumption and track changes with three sub-sections:
Consumption
Resource and AI consumption scoped to this project. Only project administrators can see this sub-section.
| View | What it shows |
|---|---|
| CPU/GPU usage | CPU and GPU hours and sessions for the selected range, with a per-user breakdown. Filter the breakdown by User. |
| Storage usage | Storage consumed by the project against its assigned space, plus a per-worker-image breakdown: latest tag, number of tags and registry space (only the latest tag counts). |
| AI usage | AI cost (USD), requests, tool calls, and token usage, with a per-user breakdown. Filter by User, Provider, and Model. |
Period: the CPU/GPU and AI views share the same period controls as the organization ones — View by (Day / Week / Month) and Detail of (the range the KPIs and tables summarise). Monthly quotas and their percentages only show on a single-month range.
Export: use the Download button to export the project's consumption as an Excel file.
AI cost limits are set at the organization level — see AI Cost Limits. Organization administrators can jump to them from Manage limits in the AI usage view.
Usage
Track how team members interact with project resources:
- Notebooks: View access patterns and usage statistics for notebooks
- Live Apps: Monitor which published applications are being accessed
- Pipelines: See pipeline execution frequency and patterns
Benefits:
- Identify most-used and underutilized resources
- Monitor team engagement and collaboration
- Optimize resource allocation based on actual usage
- Make data-driven decisions about project infrastructure
Events
View a chronological timeline of all project activities with powerful filtering and export capabilities.
Event types tracked: user additions/removals, resource creation/deletion, permission changes, configuration changes, integration updates, and other administrative actions.
Filtering options:
| Filter | Description |
|---|---|
| Event type | Filter by specific event categories. |
| User | Filter by who performed the action. |
| Date range | Preset options: Today, Last 7 Days, Last 30 Days, etc. |
| Message search | Search within event messages. |
Event details: each record includes date/time, event type (color-coded), user, affected resource, IP address, and additional properties.
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 project changes, track who did what and when, and meet compliance requirements.
API
Generate API tokens to trigger pipelines and control Live Apps from external systems via REST API.
What you can do:
- Create API tokens with specific permissions
- Call pipelines remotely from other applications or services
- Power Live Apps on, off, or into hibernation and read their state
- Automate workflows by triggering pipelines programmatically
- Integrate MINEO pipelines with external systems
Use cases:
- Trigger data processing pipelines from scheduled jobs
- Integrate with CI/CD pipelines
- Build custom dashboards that execute MINEO pipelines
- Create webhooks that respond to external events
Security:
- Each token is project-specific and scoped
- Tokens can be revoked at any time
- API calls are authenticated and logged
Advanced
The Advanced tab contains critical project management operations with two sub-sections:
Initialize
Bootstrap your project with a predefined template.
What are templates?
- Pre-configured directory structures and example files
- Help teams start projects quickly with best practices
- Include common notebooks, scripts, and folder organization
How to use:
- Select a template from available options
- Click Initialize to apply the template
- Template files and folders are added to your project
- Existing content is preserved
Common templates:
- Data Science projects with standard folder structure
- Machine Learning workflows with training and evaluation notebooks
- Custom templates created by your organization
Delete
Permanently remove the project and all its contents.
What gets deleted:
- All notebooks and their revision history
- All live apps and pipelines
- All files and datasets
- Project configuration and settings
- User access and permissions
- Activity history and logs
This action is irreversible. Once deleted, the project and all its data cannot be recovered. Make sure to back up any important data before proceeding.