Organization settings¶
Organization settings control the configuration Silico shares across an organization: its members, research guidance, service integrations, runtime environment, compute, and usage.
Open the account and organization menu in the lower-left corner of Silico and select Settings. The settings sidebar separates personal configuration under your account name from shared configuration under the organization name.
Use personal settings for credentials, instructions, and runtime values that belong to you. Use organization settings for defaults or service accounts the organization intentionally shares.
Settings and permissions¶
Every organization member can open Organization settings, but some information and actions are restricted:
| Tab | Purpose | Access |
|---|---|---|
| General | View the organization name. | Owners and admins can rename it. |
| Members | View the roster. | Owners and admins can invite people, change Member and Admin roles, and remove non-owner members. |
| Billing | View Research Unit balance and usage. | Owners and admins can purchase RUs or manage billing when those actions are enabled. |
| Cluster usage | View organization-wide GPU and storage utilization. | Available to members. |
| Compute | View the compute available to experiments. | Owners and admins manage organization-level cluster configuration; members may connect their own identity where required. |
| Custom instructions | View guidance applied across the organization. | Owners and admins can edit it. |
| Integrations | View shared service connections. | Owners and admins can connect, replace, or disconnect them. |
| Environment variables | Manage shared runtime keys and configuration. | Restricted to owners and admins. |
Owners and admins have the same access to ordinary organization settings. Ownership adds control over the Owner role itself. See Members and roles for the full permission boundary.
General¶
General contains the organization name. Use a name that members can recognize when they belong to more than one Silico organization.
Owners and admins can edit the name and select Save. Members see the current name without an editing control.
Custom instructions¶
Organization custom instructions are durable guidance for research in the organization. They are useful for conventions that should apply across many threads, such as:
- evaluation and validation practices
- coding or repository conventions
- safety requirements
- preferred reporting standards
- constraints shared by most research in the organization
Do not use custom instructions for secrets or a request that belongs to one thread.
Organization instructions apply by default. A researcher can save personal custom instructions for their own threads; Reset to organization restores the shared default.
Integrations¶
Organization integrations connect shared service accounts for supported services such as Hugging Face and Weights & Biases. Use them when the organization owns the account and expects multiple researchers to use the same connection.
Members can see the connection state. Owners and admins can connect, replace, or disconnect the account. Integration-managed tokens remain behind their dedicated cards rather than appearing as ordinary environment variables.
GitHub access is personal because it follows each researcher's repository permissions. Connect it under the account-level Integrations tab rather than as an organization credential.
Environment variables¶
Organization environment variables provide shared runtime configuration for experiment code. Use them for values that do not have a dedicated integration card.
Only owners and admins can view or change the organization variable list. Values remain masked after saving. Integration-managed names, such as the tokens used by the Hugging Face and W&B cards, must be managed from Integrations.
Members inherit organization variables at runtime. A personal variable with the same name overrides the organization value for that researcher's work without changing the shared default.
Coordinate changes to shared credentials. A rotation or removal can affect new experiments and later work that expects the previous value.
Members, billing, and compute¶
The remaining tabs have dedicated workflows:
- Members and roles covers invitations, roles, ownership transfer, and removal.
- Usage and billing covers Research Units, usage attribution, and billing actions.
- Compute covers available fabrics, linked clusters, member connections, and cluster usage.
For the researcher-facing setup flow and personal overrides, see Settings.