Onboarding
This guide covers the standard steps for bringing your team onto Linea.
Onboarding goals
A successful onboarding should:
- Get admins and users into the platform quickly.
- Confirm mailbox and domain behavior before broad rollout.
- Establish security and access controls early.
- Introduce AI and reporting features in a controlled way.
Standard onboarding flow
1. Add your initial admins
Start with a small admin group that can:
- Configure the workspace.
- Review roles and policies.
- Invite additional users.
- Coordinate with Linea during rollout.
Avoid assigning elevated access to every early user. Keep the first group intentionally small.
2. Verify your domain and mailbox configuration
Before inviting your full team, confirm:
- Domain verification is complete.
- Test mail can be sent and received.
- Shared or role-based mailboxes work as expected.
- Any migration or forwarding rules are behaving correctly.
3. Invite pilot users
Choose a small group from one team or function. Good pilot users are:
- Comfortable with new tools.
- Active email users.
- Able to give clear operational feedback.
Collect feedback on login flow, mailbox behavior, AI summaries, and any workflow blockers.
4. Introduce team workflows
Once pilot users are active, document how your team will use Linea for:
- Shared inbox handling.
- Internal escalation and ownership.
- Communication review and reporting.
- Integration-driven workflows if API access is enabled.
5. Launch broadly
After pilot validation, expand access in phases:
- Team by team.
- Domain by domain.
- Or all at once if your organization is ready.
For larger rollouts, publish a short internal launch plan with support contacts, expected cutover timing, and known limitations.
Suggested first-week checklist
- Confirm all admins can sign in.
- Confirm key users can send and receive mail.
- Review access logs or activity reports if available.
- Validate shared mailbox ownership.
- Confirm billing and subscription contacts are correct.
- Log open questions for the Linea team.
Common onboarding best practices
- Start with a pilot group before full deployment.
- Use role-based access instead of shared credentials.
- Document domain and mailbox ownership.
- Schedule a post-launch review after the first week.
For account permissions and authentication planning, see Access.