Moderating who joins your organization
Control whether people can self-join with a link, need admin approval, or must use an allowed email domain — so your Dailybot org matches your company’s access policy.
Before you begin
- You need Organization admin access.
- Decide your policy: fully open self-join, approval queue, domain allowlist, or a combination (many teams use domain restriction plus approval for exceptions).
Steps
- Open the Dailybot web dashboard and sign in as an org admin.
- Go to Organization and open the settings area for Members, Access, or Join (wording varies slightly by product version).
- Configure open join: Enable the option that allows anyone with the invite link to join without a manual review. Disable it when you want every new member to be explicitly approved or invited.
- Configure approval required: Turn on join requests or pending approvals so each signup waits for an admin (or delegated role) to accept or deny. Set notifications if offered so requests are not missed.
- Configure domain restriction: Add allowed email domains (for example
yourcompany.com). Save changes so accounts outside those domains cannot complete self-join; they will need a direct invite from an admin or a policy exception. - Review related options such as default role for self-join (often Member) and whether managers can approve joins if your plan supports delegation.
- Test with a secondary account or a colleague: try the public link, a non-matching domain, and an allowed domain to confirm behavior matches intent.
- Document the live invite link and approval process for your internal IT or People team so onboarding stays consistent.
What to expect after
With open join off and approval on, your Members list grows only after you act on pending users. Domain rules stop surprise signups from personal email providers while still letting you invite specific people by email or chat when needed. Changes apply to new join attempts; existing members are not removed when you tighten settings.