View team members
The team list shows:
- Name — User’s display name
- Email — Their account email
- Role — Permission level (Admin, Member, etc.)
- Status — Active or pending invitation
Invite team members
The invited user receives an email with instructions to join.
Pending invitations
View and manage pending invites:- Resend — Send the invitation email again
- Cancel — Revoke an invitation before it’s accepted
- Expiration — Invitations expire after a set period
Roles and permissions
Team members have different access levels:| Role | Capabilities |
|---|---|
| Admin | Full access including settings, team management |
| Member | Full access to clients and data, limited settings |
| Read-only | View data but cannot make changes |
Change a user’s role
Note: Only admins can change roles. The book principal’s role cannot be changed.
Remove team members
What happens when someone is removed
- They immediately lose access to the book
- Tasks assigned to them remain (can be reassigned)
- Notes and activities they created remain
- Their user account continues to exist (just without book access)
Reassign their work
After removing someone, consider:- Reassigning their open tasks
- Updating workflow assignments
- Reviewing any pending items they owned
User profiles
Each team member has a profile that affects their Slant experience:Profile information
- Name — Display name in Slant
- Email — Account email (used for notifications)
- Avatar — Profile picture
User-specific settings
Each user manages their own:- Notification preferences
- Email signature (via integration)
- Default views and layouts
Multiple books
If your firm has multiple books:- Users can be members of multiple books
- Roles may differ per book
- Switching between books is available in the header
Add someone to another book
The admin of each book must invite users separately. Being a member of one book doesn’t grant access to others.Team size and limits
Team member limits depend on your plan:| Plan | Team Members |
|---|---|
| Basic | Limited |
| Pro | Expanded |
| Enterprise | Unlimited |
Best practices
Use meaningful roles. Match permissions to actual job responsibilities. Don’t give everyone admin access. Clean up departures promptly. Remove access when team members leave to maintain security. Document responsibilities. Keep track of who handles what, especially for task assignments and workflow ownership.Troubleshooting
Invitation not received
Causes:- Email went to spam
- Typo in email address
- User already has an account with different email
Can’t change someone’s role
Causes:- You don’t have admin permissions
- Trying to change the principal’s role (not allowed)
User can’t access the book
Causes:- Invitation not accepted
- Account deactivated
- Different email used to log in