Invite a team member and define company access in 6am

Outcome and ownership

A named person can sign in with a verified email and access only the approved company with an appropriate role. The company administrator owns the invitation and the access check; the recipient verifies their own email and accepts. Record approval, company, recipient, role and purpose in your internal access register before sending.

01. Confirm the company and least privilege

1. Sign in at app.6am.ag and select the intended company in the company menu. Confirm its name before any invitation. For company setup, use SOP 003.
2. Open Team management → Company members and check whether the person already belongs to this company. An existing member needs a role review, not another invitation.
3. Define the work they need to perform. Admin includes company administration, member management and CRM permissions; assign it only when those capabilities are required. User has no administrative or CRM permissions by default. It is not a ready-made sales role. Choose an available custom role for specific duties, or ask the platform administrator to provision one before inviting.
4. Role permissions are not the whole story: direct permissions and team permissions, where configured, can also contribute to effective access. Do not promise record-level, assigned-leads-only access from a role name. The invitation screen only offers roles the inviter is allowed to grant.

02. Send the invitation

1. Open Team management → Invitations → Create. Confirm the company again.
2. Enter the recipient's exact work email. A batch supports up to 25 distinct addresses, separated by commas or line breaks; repeated addresses are combined without creating another invitation. Every address in the batch receives the same selected role. Split batches when responsibilities differ.
3. Select the role. If a Team selector is enabled, select only an approved team in this company and check its additional permissions. Submit only after reviewing all recipients: creating invitations sends email notifications.
4. Check the new Pending records, role, inviter and expiration. Invitations expire after 7 days. Pending invitations do not prove access or delivery to the inbox. Subscription seat limits are checked again at acceptance; seat-based plans may adjust billed quantity when members join or leave.
5. If the email or role is wrong, use Cancel invitation, confirm, and create a corrected invitation. Cancelled, accepted, rejected and expired records remain in the history; do not erase that history as a routine cleanup.

03. Recipient verifies and accepts

1. Open the invitation email and sign in at 6am invitations with the same email that was invited. If an account is needed, create it using that address. The recipient sets their own password; administrators do not exchange passwords.
2. Complete email verification. If needed, request the verification email from the verification screen. Then return to Invitations. Another signed-in address will not show or accept this person's invitation.
3. Confirm the company and inviter, then choose Accept. Use Reject if the invitation is unexpected. Expired, cancelled or already consumed invitations cannot grant access. An invitation can also become unavailable if the inviter loses permission or its role/team is no longer valid.
4. Select the company and perform one permitted task. Ask the administrator to confirm membership and role in Company members. Do not infer that an email was delivered just because a record is Pending.

04. Acceptance checks and troubleshooting

Pass criteria: the recipient is a member once, the intended role applies only to the approved company, one required task succeeds, and at least one forbidden administration action is unavailable or denied. Check each company separately using SOP 007.

• Invitation not visible: confirm the exact signed-in email, its verification and the company/expiry shown to the inviter. Request a corrected invitation when necessary.
• No email: check spam, address and the application's mail/queue status with the platform administrator. Do not repeatedly create invitations or run historical message queues to troubleshoot.
• Acceptance unavailable: review expiration, cancellation, existing membership, the inviter's current authority, role/team availability and subscription capacity. Cancel and replace only after correcting the cause.
• User cannot access CRM: the default User role does not grant CRM permission. Review the approved role; do not promote to Admin just to hide a missing permission.

For QA, use synthetic accounts and controlled inboxes with explicit authorization for messages. This SOP does not provision external email accounts, promise inbox delivery, or grant access to every company in the platform. Keep the access approval and the verification outcome in your internal register without storing passwords or invitation secrets.