SSO, SAML, and SCIM for Dailybot (enterprise sign-in)
Dailybot is delivered as a chat-native product, so the default sign-in for every member is the chat workspace itself (Slack, Microsoft Teams, Discord, or Google Chat). Those platforms already enforce your company’s SSO and identity policies.
That covers what most teams need. If your security team requires SAML enforced inside Dailybot’s web app or automatic provisioning via SCIM, those are enterprise plan features – read on.
How sign-in works today (default)
| Surface | Who controls authentication |
|---|---|
| Dailybot in Slack | Slack workspace (which already inherits your IdP and SSO) |
| Dailybot in Microsoft Teams | Microsoft 365 tenant (Azure AD / Entra ID) |
| Dailybot in Discord | Discord account |
| Dailybot in Google Chat | Google Workspace |
| Dailybot web app | Same identity used to install in chat (re-uses the chat session) |
Result: when you remove a user from Slack/Teams/Google/Discord, they lose access to Dailybot too. That is the inherited SSO model, and it satisfies most SOC2 access-control controls without extra setup.
When you need native SAML or SCIM
| Need | Available? |
|---|---|
| SAML enforced on the Dailybot web app, independent of chat session | Enterprise plan (contact sales) |
| SCIM automatic user provisioning / de-provisioning from your IdP (Okta, Entra ID, JumpCloud, etc.) | Enterprise plan (contact sales) |
| Just-in-time (JIT) user creation on first SAML login | Enterprise plan |
| Force re-auth on a schedule (session timeout) | Enterprise plan |
| Audit log of admin actions and sign-ins | Enterprise plan |
If your auditor or IT team wants a quote, an architecture review, or a security questionnaire response (SOC2, ISO 27001, HIPAA), contact Dailybot sales or support with:
- Your org name and plan.
- Your IdP (Okta, Entra ID / Azure AD, Google Workspace, OneLogin, Ping, etc.).
- Number of users.
- Required compliance frameworks.
What sales/support will ask back
- Identity provider and protocol (SAML 2.0 / SCIM 2.0).
- Whether you need JIT provisioning or full SCIM lifecycle.
- Domains to be claimed for verified-domain enforcement.
- Whether existing users should be migrated to SAML or run in parallel.
- Target go-live date and any audit deadlines.
What does NOT change
- Members still interact with Dailybot through their chat platform daily. SSO/SAML is for the web app and provisioning workflows.
- Per-user roles (Member, Team Manager, Org Admin) are still managed in Dailybot. SCIM can sync users, not Dailybot-specific roles unless your contract includes role mapping.
- Billing is org-level, not per-IdP.
Until enterprise SSO is enabled for your org
If you are on a non-enterprise plan and an auditor asks “is SSO enforced?”, the correct answer is yes via the chat platform (inherited SSO). See Compliance overview and your DPA for the formal wording.