Hane Cowork

Administration

How organization administrators configure Hane Cowork access, models, quotas, and rules for local capabilities, and what to consider when rolling it out.

This page is for administrators who enable Cowork for their organization. It describes the Cowork policy settings and how to change them, the permissions users need, and what to consider when rolling Cowork out.

The Cowork policy

There is one Cowork policy per project and environment. A user’s Cowork follows the policy of the project and environment of the access token used to connect.

Field	Meaning	Default
`enabled`	Whether Cowork model access is enabled	`false`
`models`	Models Cowork may use. Only models available in the Model Gateway can be set	none
`daily_token_limit`	Tokens the whole project can use per day (UTC)	100,000
`session_token_limit`	Tokens one model session can use. Cowork creates a model session for each request	25,000
`max_output_tokens`	Maximum output tokens per call	4,096
`local_tools`	Rules for each local capability (see below)	all `deny`

In local_tools, set allow, confirm (ask the user every time), or deny for each of these five capabilities.

Key	UI name	Scope
`files`	「作業フォルダのファイル」 (Work-folder files)	Reading and writing in the work folder the user chose
`commands`	「コマンドの実行」 (Run commands)	Running local commands (Cowork does not provide this tool yet)
`browser`	「Chrome の操作」 (Chrome actions)	Reading and operating shared Chrome tabs
`computer`	「PC の操作」 (Computer use)	Capturing and sending input to the chosen app
`external_transfer`	「外部への送信」 (External transfer)	Sending local content outward, for example by typing into a page

If no policy is set, or enabled is false, every local capability is treated as denied. For how each capability behaves, see Confirmations and organization policy.

Cowork uses the first model among the configured models that is currently available in the Model Gateway (available_models). Users cannot choose a model.

Changing the policy

Read and write the policy through the API. There is no Console screen for it yet.

Operation	API	Required scope
Read	`GET /v1/cowork/policy`	`cowork:run` or `cowork:manage`
Change	`PUT /v1/cowork/policy`	`cowork:manage`

To change it, first read the current policy with GET and send its version in If-Match. If someone else changed the policy first, the request fails without saving.

PUT /v1/cowork/policy
Authorization: Bearer <access token>
If-Match: "3"
Content-Type: application/json

{
  "enabled": true,
  "models": ["<Model Gateway model name>"],
  "daily_token_limit": 200000,
  "session_token_limit": 60000,
  "max_output_tokens": 2048,
  "local_tools": {
    "files": "allow",
    "commands": "deny",
    "browser": "confirm",
    "computer": "deny",
    "external_transfer": "deny"
  }
}

If you omit local_tools, the saved rules for local capabilities stay as they are. Get the access token for the project and environment you want to configure (Authentication).

Each time a user’s Cowork uses a tool, it decides using a policy read within the last 5 seconds. Policy changes reach running work within seconds.

Permissions users need

Using Cowork requires cowork:run. Among the built-in roles, developer, operator, admin, and owner have it; viewer does not. cowork:manage, which changes the policy, is held by admin and owner.

Cowork’s model credentials expire after 5 minutes, and Cowork refreshes them before they expire. On each refresh, Platform rechecks the user’s permissions, the policy, and the remaining quota. If the user is suspended or loses cowork:run, the refresh is refused and running work can no longer call the model.

Usage and records

Each model call is recorded and its quota reserved before it is passed upstream. When the call ends, the reservation is replaced with actual usage. When the limit is reached, the user sees 「モデルの利用上限に達しました。組織の利用状況を管理者に確認してください。」 (Model usage limit reached. Ask your administrator about the organization’s usage).

Call records keep the model, outcome, input and output token counts, and latency. They do not keep request or reply text, file names, or credentials.

Rollout considerations

Builds are unsigned. There is no macOS notarization, Windows signing, or automatic update yet. Check that this fits your device management policy.
Sign-in is provisional. Users enter the Platform URL and an access token. Regular sign-in and token refresh are not available yet.
Start narrow. We recommend setting only files to allow or confirm and leaving everything else at deny at first. browser and computer are preview features (Use your everyday Chrome, Operate apps).
Windows has no OS sandbox. On macOS, the OS restricts the harness’s network access and writes; Windows does not have an equivalent restriction yet.
History stays on the device. Conversation text and work records are saved in the app data on the device. Assume disk encryption on the device.
Local actions are not in Platform audit logs. Only model call records are kept. There are no finer rules per folder, site, or app yet.
OS permissions are required. Computer use needs the macOS Screen Recording and Accessibility permissions.

To uninstall, disconnect Chrome in Cowork, remove the app, and also delete its app data directory. You do not need to create any cloud resources or accounts in your organization for Cowork.

Next steps

How Cowork keeps things safeCredentials, network, and OS restrictions

Model GatewayModel access on Platform

Availability and limitationsCurrent status of each feature