How StretchSuite protects your account and workspace

The core idea: org-scoped access

The single most important security property on StretchSuite is that every session is organization-scoped. When you sign in, your session is bound to one active organization at a time, and the platform resolves what you can see and do against that organization only. If you belong to several organizations, their data never bleeds together — switching organizations changes the entire context. This is what keeps one client's data invisible to another, even under the same account.

How your session is protected

Server-side verification. Your email and password are checked against the platform, not trusted from the browser. A valid session is issued only after that check passes.
Route-level auditing. Actions are attributable to your account within the active organization, so access can be reviewed. This accountability is a deterrent as much as a record.
Server-resolved entitlements. What your workspace can open (which apps and features) is decided on the server based on the organization's plan and your role — not something the browser can toggle on. Even if a locked app's page is reached directly, access is gated server-side.
Scoped memberships. Your role and permissions are attached per organization, so being an owner in one workspace grants you nothing extra in another.

What you control

Security is shared between the platform and you. Your part:

Use a strong password. The minimum is 10 characters; longer passphrases are stronger. Don't reuse a password from another service.
Choose "Keep me signed in" deliberately. Leave it on for your own trusted devices; turn it off on shared or public ones.
Sign out on devices that aren't yours. Ending the session prevents someone from reaching your workspace after you step away.
Protect verification and reset links. They contain one-time tokens tied to your account — don't forward them.
Keep your role appropriate. If you're an owner or admin, you can grant far-reaching access; grant only what teammates need (see Roles: owner, admin, and member explained).

Realistic example

An agency manages two clients, Brightpath and Riverside, in separate StretchSuite organizations. Their operations lead, Sam, is an admin in both. While working in Brightpath, Sam can see Brightpath's CRM, files, and invoices — but nothing from Riverside, because the session is scoped to Brightpath. To help Riverside, Sam switches workspaces, and the context flips entirely. If Sam's laptop were ever misused, the route-level audit trail would attribute actions to Sam's account, and signing out ends the session so a passer-by can't continue it.

Tips

A passphrase beats a complex short password. Four unrelated words are easy to remember and hard to guess, and they clear the length minimum comfortably.
Never share one login. Give each teammate their own account and role. Shared logins destroy the audit trail and over-grant access.
Switch context before sensitive work. Confirm the active organization on /account so you never act in the wrong workspace.

About SSO

Single sign-on appears on the sign-in screen but is currently gated (disabled) during the rollout. Until it's enabled, email-and-password with a strong, unique password is your protection. When SSO becomes available, it will add another managed sign-in path; the org-scoping and auditing described here remain in force regardless.

FAQ

Is there two-factor authentication? The current sign-in path is email and password, with SSO gated for a later phase. Protect your account with a strong, unique password and by signing out on untrusted devices. Watch platform announcements for additional authentication options as the rollout matures.

Can an admin see my password? No. Passwords are verified by the platform, not readable by admins or support. If you're locked out, use the reset flow rather than asking anyone for your password.

If I leave an organization, can I still see its data? No. Access is tied to your active membership. Remove the membership and the org-scoped session can no longer resolve that workspace for you.