Set up company Operations alongside team work

Establish operational ownership, connected services, and a review routine.

Spaces helps colleagues carry out shared work. Operations gives the people responsible for company systems and administration a place to maintain resources, connections, and oversight. Set both up around real responsibilities.

1. Choose the responsible operators

Identify who owns company access, provider connections, resources, and operational reporting. These responsibilities can belong to a few people in a small company. They do not all need the same permissions.

In Team, configure Operations access and the relevant scopes. Use the minimum organization role that permits the required feature. Test the actual operation: viewing a provider, changing its configuration, and disconnecting it can have different requirements.

2. Connect the services you actually use

Open Integrations and choose the appropriate provider-specific guide. Establish which company account should own the connection and which data the team expects to see.

For example, Make setup includes selecting the relevant organization and team, while OpenAI cost reporting uses different credentials from the OpenAI Assistant Key. Do not substitute a general API key for a provider’s required reporting or management credential.

After connecting, verify the expected account and data. A successful authentication test is not the same as proof that every expected resource has synchronized.

3. Record the operational context

Use Registry for supported company resources and the appropriate operational views for system relationships or technical workflows. Keep credentials in the supported Secrets workflow, with its required administrative access, rather than in task descriptions or shared notes.

Where the team needs to follow up, create clear tasks in the owning department’s project. For example, put Review the disconnected reporting integration in IT & Systems rather than relying on someone to notice a dashboard warning indefinitely.

4. Review reports in context

Use the Operations Dashboard and provider reporting for the questions they support. Confirm the selected provider, account, and reporting period before interpreting cost or usage figures. Do not describe a budget field as an enforced spending cap unless that behavior is verified for the deployed product.

Use Audit to investigate recorded actions when your access permits it. Use assessments and evidence according to their available, verified workflow; retained technical references may require additional release checks before publication in the help center.

5. Establish ownership for maintenance

Record who will renew or replace credentials, investigate connection errors, and review access. Recheck the configuration when the responsible person changes roles. Disconnecting a provider or rotating credentials is an operational change, so use the dedicated procedure and required permissions.

You are finished when: operators can explain what each connection supports, confirm the expected data, and turn an issue into owned work for the appropriate team.