This page provides an overview of the rollout process. Your agreement with Almanac determines specific terms, features, and timelines.
Plan your rollout
Before inviting members, complete the agreements and security review required by your organization. Ask the Almanac team for current information about architecture, data flows, subprocessors, and where data is processed.
Define the initial scope of the rollout at the same time. A department may need a small group of administrators and a shared configuration. A health system may also require directory provisioning, role mapping, managed settings, and separate owners for each part.
Set up identity and access
Most organizations use single sign-on with their existing identity provider. This keeps access aligned with the process your organization already uses when someone joins or leaves.
Decide:
- Who provisions members: Choose whether access is granted by an administrator, through directory groups, or through approved self-service enrollment.
- What each role can do: Define administrators, members, and the organization-wide permissions that apply to them.
See Authentication, Groups and provisioning, and Roles and access.
Set data and retention policies
Review what Almanac stores, how long it is retained, and what happens when a member leaves.
Decide whether anyone other than the author may access a member’s conversations and how conversations and files should be retained, exported, or removed.
See Privacy and data.
Set up billing
Organization plans use centralized billing and report usage to the organization. See Usage and billing for information about plans and usage.
Contact Almanac
Enterprise rollouts are planned with the Almanac team. Email hello@almanac.chat with your organization, identity provider, and estimated number of members.