Skip to main content
Organization admins manage members, access, integrations, and compute budgets from the Settings page at app.tamarind.bio/org-settings. To open it, click Organization in the left sidebar of the app. The settings menu is grouped into four sections:
Most settings on this page require the Admin role. Numbered markers in each screenshot match the numbered items in the text.

​
Organization

​
Members

See everyone in your organization and manage their roles.
  1. Members / Invitations — switch between current members and pending invitations.
  2. Invite — invite new people to your organization by email.
  3. Role — change a member between Admin and Member. Use the ⋯ menu in the Actions column for other options.
Use the Search bar to find a member by name or email. Members page

​
Sharing Permissions

Control who can see jobs and budget information. Click Save Permissions at the bottom of the page after making changes.
  1. Allow organization members to see each other’s jobs — when on, members can see and access jobs created by others in your organization. When off, members only see their own jobs.
  2. Allow organization members to share with users outside of organization — when on, members can share jobs with people outside your organization. When off, jobs can only be shared internally.
A third setting, Allow organization members to see budget in compute report, lets non-admin members see budget figures (annual budget, budget remaining, monthly budget) in the compute report. When off, only admins see budget information. Sharing Permissions page

​
Teams

Group members into teams to collaborate and to apply shared budgets.
  1. Organization Members — every member and the teams they belong to.
  2. Default team for new members — new members are added to this team automatically.
  3. Create Team — create a new team.
Each team card shows its members and compute usage against the team’s limit. Click Add Members on a team to add people. Use Set Individual Budget by Team at the bottom of the page to give every member of a team the same individual budget. Teams page

​
Service Accounts

Create API keys for programmatic access — for example, from CI/CD pipelines, scripts, and other automated systems.
  1. Create Service Account — create a new service account and API key.
  2. Rotate / Delete — rotate a service account’s API key, or delete the service account.
Each service account shows the last four characters of its API key, when it was created, and who created it. Service Accounts page

​
Projects

Control how projects work across your organization. Click Save Settings (3) after making changes.
  1. Disable projects for this organization — hides the project column, project filter, and project management for all members.
  2. Require all jobs to be tagged to a project — every job must be tagged to an existing organization project at submission time. Untagged jobs, or jobs tagged only to a personal project (including via the API), are rejected. Personal projects don’t count because org admins can’t see them. This setting has no effect while projects are disabled.
Projects settings page

​
General

  1. Update profile — edit your organization’s profile.
  2. Leave organization — remove yourself from the organization.
General page

​
Single Sign-On

Connect your identity provider (Okta, Microsoft Entra ID, Google Workspace, or another SAML provider) so your team signs in with their company account. For step-by-step instructions, see Set up Single Sign-On (SSO). Single Sign-On page

​
Integrations

​
S3 Results Integration

Automatically upload job results to your own Amazon S3 bucket. Results for each member are uploaded to the path user@email.com/JobName/file.txt.
  1. Instructions for S3 Bucket Setup — expand for the bucket policy that grants Tamarind access to your bucket.
  2. Bucket Name — the name of your S3 bucket.
  3. Result uploading enabled — turn uploads on or off.
Click Save to apply your changes. S3 Results Integration page

​
S3 Input Integration

Connect read-only S3 buckets so your team can browse and select input files when submitting jobs. Files in these buckets appear in a new S3 Input tab in the file picker.
  1. Instructions for S3 Input Bucket Setup — expand for setup steps.
  2. Bucket — enter the Bucket Name and Bucket Region (for example, us-east-1). Optionally click Add Prefix to limit which folders are listed. Leave prefixes empty to list from the bucket root.
  3. Add Bucket — connect another bucket.
Make sure S3 Input Integration enabled is checked, then click Save. S3 Input Integration page

​
GCP Integration

Automatically upload job results to Google Cloud Storage, at gs://your-bucket/user@email.com/JobName/.
  1. Setup Instructions — expand for setup steps.
  2. Enable GCP Storage Integration — turn uploads on or off.
  3. GCS Bucket Name — the name of your Google Cloud Storage bucket.
  4. Upload Service Account JSON — upload the service account JSON key file you downloaded from the Google Cloud Console. The key is stored securely.
Click Save GCP Configuration to apply your changes. GCP Integration page

​
GitHub Integration

Choose which GitHub accounts your organization can pull source code from (for example, for custom tools).
  1. Add GitHub account — install the Tamarind GitHub App on a GitHub user or organization account.
  2. Allow members to manage their own GitHub integrations — when on, members can install the GitHub App on new accounts and remove integrations they installed. When off, only admins can manage GitHub integrations.
Each connected account shows its type (User or Organization), whether it’s Org-wide or Personal, how many repositories are accessible, and who installed it. Click Manage to change repository access. GitHub Integration page

​
Webhooks

Send real-time job event notifications to your internal systems. Click View documentation for payload details.
  1. Endpoint URL — the URL that receives events.
  2. Events — choose which events to send:
    • Jobs: Completed, Stopped / failed, Created, Running
    • Batches: Completed, Stopped
    • Pipeline runs: Completed, Partial, Stopped / failed
  3. Enabled — turn delivery on or off. Events are delivered only while the endpoint is both enabled and verified.
  4. Actions — Create webhook, then Verify endpoint. Use Send test event to check your endpoint, and Rotate secret to replace the signing secret.
The Recent deliveries table below shows each event, its job, delivery status, last response, and time. Webhooks page

​
Tools

​
Access Management

Manage which tools are available to your organization, teams, and individual people from a single grid. Hidden tools are blocked unless you grant an exception, and the strictest rule wins.
  1. New & unconfigured tools — choose Allow to make newly released tools available by default, or Block to hide them by default.
  2. Search tools / Filter teams — find specific tools or teams.
  3. Access grid — click a cell to flip access. Click a tool’s person icon to set access for individuals, or a team’s column header for bulk actions.
The legend explains each state: Available, Blocked for team, Hidden org-wide, Exception granted, and Following org default. Access Management page

​
Custom Tools

See every custom tool in your organization, control who can see them, and publish or unpublish versions.
  1. All members can view all custom tools — on by default. When off, members only see custom tools they created or were given access to. Org admins can always see all tools.
  2. Search — find a tool by name, owner, or person.
  3. Publish — publish a draft or a new version. Click Open to edit a tool, or expand a row to manage per-tool access.
Custom Tools page

​
Compute Budgets

Compute usage and budgets are measured in weighted hours — compute hours weighted by the compute type used.

​
Usage Report

Track compute usage across your organization.
  1. Organization / My Usage — switch between organization-wide usage and your own.
  2. Time range — choose All Time, Contract (pick a contract period), or Custom.
  3. Metric — view Hours (weighted by compute type used), Jobs, or Cumulative totals.
  4. Export CSV — download the data.
The top of the report shows hours used, the budget for the period, and hours remaining, with a breakdown by tool. Use the By Tool, By User, By Team, and By Project tabs to break down usage over time. Click Refresh Data to load the latest numbers. Usage Report page

​
Your limits

A read-only summary of the compute budgets that apply to your own jobs.
  1. Read only — contact your organization admin to change these limits.
  2. Personal & per-batch — your individual allowance per budget period and the budget for each batch submission.
The page also lists the Organization budget shared by all members, shared budgets for Your teams, and Models budgets. A job must fit within every limit that applies. Your limits page

​
Budget Alerts

Get email reminders when your organization reaches a percentage of its compute budget.
  1. Reminder type — choose Monthly reminders (percent of the monthly budget used) and/or Contract-term reminders (percent of the full contract budget used).
  2. Percentage — enter a percentage and click + to add a reminder threshold. Click the trash icon to remove one.
  3. Save Reminders — apply your changes.
Budget Alerts page

​
Default Budget Limits

Set organization-wide default limits. Members are blocked from submitting jobs once they exceed these limits.
  1. Per-Person Budget — the maximum weighted hours per member for each budget period. Click Set Budget to change it.
  2. Per-Batch Budget — the default budget for each batch submission.
Default Budget Limits page

​
Model Budgets

Cap compute usage for specific models. Jobs using a model are blocked once that model exceeds its budget.
  1. Search models — find a model by name.
  2. Set Budget — set a weighted-hour limit for that model. Each row shows the model’s current usage.
Model Budgets page

​
Individual Budgets

Override the default per-person budget for specific members for the current budget period.
  1. Add Individual Budget — select a member, enter a budget in hours, choose the period, and click Add.
  2. Set Budget by Team — select a team and apply the same individual budget to all of its members.
Individual Budgets page

​
Need help?

Click Support in the app sidebar.