# Shared essentials

Use these guides when a task crosses account, device or data boundaries. Keep the product-specific procedure open beside them: shared guidance does not replace that product's access checks or result verification.

## Find the boundary you need

- [Account and access](/docs/shared/account): sign in to the intended account, approve a native connection and recognize paid-access restrictions.
- [Policy Hub](/docs/shared/policy-hub): write durable rules, verify saved versions and inspect runtime authority separately.
- [Privacy and permissions](/docs/shared/privacy): identify what the selected action can read, change or send.
- [Local files, hosted processing and model requests](/docs/shared/local-files-hosted-processing-and-model-requests): follow the data path before choosing an action.
- [Get help without losing work](/docs/shared/support): retain drafts and operation identities, then share a sanitized report.

## Before changing access or permissions

Ouros X is free to use. Separately paid services have their own requirements: Zilch extraction needs active paid Zilch entitlement. A successful sign-in, provider key or available quota does not substitute for it.

A configured folder limits file search; it does not sandbox arbitrary commands. A written instruction describes intent, not operating-system enforcement. Review the specific feature before submitting sensitive input or starting work that changes files.

## Continue in the owning product

Once you identify the boundary, return to the original task and check its own result. A connected account is not a saved file; an accepted request is not completed work. For an intentional transfer between tools, follow [cross-product workflows](/docs/workflows).