Account security for your team

Your organization's security posture is the combination of what OrganizeOS provides by default, what your members control on their own accounts, and what you configure as an admin. This page walks through the admin-facing pieces. Open Settings, then Security in your workspace sidebar to find the two-factor and idle-timeout controls; default message retention lives on the main Settings page.

What every member gets by default

You don't have to configure these; they apply to every account in your organization automatically.

Encryption at rest protects every message in your channels, DMs, and groups. The platform encrypts content before writing it to the database; a database breach returns ciphertext, not plaintext. See message encryption and security posture for the full model, including what OrganizeOS can decrypt and when.

Login history and new-device alerts are on for everyone. Every successful sign-in is logged, and any sign-in from an unfamiliar device for a member triggers an email to that member with the device and IP details. Your members will see this on their own Security tab; you don't see their individual login activity.

Session tracking lets every member see and revoke their own active sessions. There is no platform-wide cap on concurrent sessions; by design, members are expected to be signed in on phone and laptop simultaneously.

What is required for owners and admins

Two-factor authentication is required for anyone with an owner or admin role in your organization. The platform enforces this at sign-in: until they enroll, they cannot continue past the login screen. See enforcing two-factor authentication for how to verify enrollment status across your team and what the user experience looks like.

This is the one platform-level requirement we don't let you opt out of. The blast radius of a compromised owner or admin account is too large to leave to discretion.

What you can configure

Four policies, split across two settings pages:

Two-factor authentication for the rest of your team (Settings, then Security). Owners and admins are always required, but you can extend the requirement to staff, employees, and organizers too. Choose Off (voluntary), Grace period for new members (a configurable window of 1-90 days before enrollment is enforced), or Fully required. This does not affect supporters or regular members. See enforcing two-factor authentication for how the policy combines with the owner/admin requirement.

Idle session timeout (Settings, then Security) signs members out after a period of inactivity, configurable from 5 minutes to 8 hours, or off entirely. See session idle timeout for the details, including the "trust this device for 30 days" affordance and how it composes for members of multiple orgs.

Default message retention (main Settings page) sets how long messages in new channels are kept before they're hard-deleted. You can pick 24 hours, 7 days, 30 days, 90 days, 1 year, or "keep forever" (the default). Existing channels are not retroactively changed; this only applies to channels created after you change the setting. See message retention and disappearing messages.

Per-channel retention overrides (each channel's own Settings dialog) let channel admins shorten or lengthen retention on that specific channel below the org default. DMs and group chats have their own retention controls instead: two-person DMs use a mutual-consent flow (each participant proposes a window; the shortest non-null proposal wins), while group chats let a group admin set the window directly, the same way a channel admin does.

What we do NOT offer, and how to verify your posture

By design, OrganizeOS does not provide the following. If you need any of them, OrganizeOS may not be the right tool for the relevant conversations.

End-to-end encryption. OrganizeOS can decrypt messages with the master key for moderation, audit, and lawful requests. For conversations where the platform itself should not be able to decrypt, your members should use Signal or Matrix. We tell them so in the in-app explainer.

A concurrent-device cap. Members can be signed in on as many devices as they want. We surface active sessions for transparency, but we don't enforce a maximum. Capping concurrent logins is hostile to legitimate use (phone + laptop) and only weakly slows attackers.

SAML / SSO. Federated identity is on the roadmap but not shipped. Members authenticate with email-and-password or magic link directly with OrganizeOS today.

To verify your posture, walk through your own Security tab as a member would (/dashboard/settings?tab=security). Confirm: two-factor authentication is enabled on your account, you have recovery codes stored somewhere safe, your active sessions list matches what you expect, and your recent sign-ins look right. Then, in your workspace settings, confirm the org-level idle timeout and default retention windows are set to values that match your organization's policy.

Why this matters

A small organization's security posture is rarely undone by a sophisticated attack; it is usually undone by an undefended account belonging to someone with admin access. The defaults here close the most common failure modes (no 2FA on an admin, no notification when an attacker gets in) without requiring a security team to operate. The configurable pieces let you tighten further for the specific conversations your org has.