Accounts, devices and security

Before you begin

• Your own verified account and access to its sign-in method.
• Your own authenticator for MFA and a supported native device for enrollment.

Step by step

1. Sign in to your own account

   Use an available configured sign-in method and complete required email verification. Provider sign-in establishes identity, not permission to access provider files.

2. Review the selected space

   Choose personal or an authorized Organization. Your role controls access; an invitation must be accepted through the verified identity flow.

3. Review devices and current limits

   Open device management to inspect authorized runtimes. Check the current account plan/device allowance rather than assuming seats equal device slots. Browser account viewing does not enroll a native runtime.

4. Enroll or remove deliberately

   Authorize your native installation through its sign-in/enrollment flow. Review any device removal carefully and complete MFA where required; do not remove the only device holding unsaved local work.

5. Secure keys and sessions

   Set up and verify your own authenticator before sensitive operations. Keep the encryption recovery key separate from the authenticator and account password; each serves a different purpose.

Expected result

The correct signed-in space, reviewed devices and verified MFA for protected operations, without changing plan limits.

Privacy and permissions

Recordings, files, searches, scans, OCR, barcode counts and supported local-AI results do not leave the device by default. Only a deliberate online action—Share, Search online, connector authorization or encrypted backup—transmits the selected data or value. Language-pack downloads do not upload the source text. Account and device metadata coordinate authorization online. Customer-content inference remains local; sharing Organization membership does not grant unrestricted access to every personal file.

Troubleshooting