Permissions

Permissions control what team members can see and do in your Slant book. Assign roles that match each person’s responsibilities to maintain security while enabling collaboration.

​

Permission roles

​

Principal

The book owner with full control:

• Cannot be removed from the book
• Always has admin permissions
• Created the book or was assigned ownership

​

Admin

Full access to the book including settings:

• Manage team members and invitations
• Configure book settings
• Create and modify custom fields
• Access all client data
• Run any automation

​

Member

Standard access for day-to-day work:

• Full access to clients, prospects, and contacts
• Create, edit, and complete tasks
• Send emails and schedule meetings
• Use workflows and sequences
• Cannot access admin settings

​

Read-only

View access without edit capability:

• View client records and activity
• Cannot create or modify data
• Cannot send communications
• Useful for compliance or oversight roles

​

Permission comparison

​

Assign permissions

Note: Only admins can change user roles.

​

Permission guidelines

​

Who should be an admin

Give admin access to:

• Practice principals and partners
• Office managers who configure the system
• IT staff who maintain integrations

​

Who should be a member

Standard member access works for:

• Advisors working with clients
• Support staff managing tasks and communications
• Operations team handling data entry

​

Who should be read-only

Read-only access is appropriate for:

• Compliance officers who need to review records
• Executives who want visibility without editing
• Temporary staff or contractors

​

Record-level access

Beyond roles, some access is controlled at the record level:

​

Task assignments

Users see all tasks but can filter to show only their assignments.

​

Private notes

Notes can be marked private, visible only to the creator and admins.

​

Workflow permissions

Some workflow actions may be restricted based on the triggering user’s permissions.

​

Data visibility

​

What everyone can see

All team members can view:

• All household records
• Contact information
• Task lists and calendars
• Notes and activities

​

What’s role-restricted

Only admins can see or modify:

• Team member list
• Integration settings
• Custom field configuration
• Book-level settings

​

What’s user-specific

Each user only sees their own:

• Email integration settings
• Personal notification preferences
• Draft emails and unsent messages

​

Audit and accountability

​

Activity tracking

Slant tracks who makes changes:

• Record creation and modification
• Task completion
• Note authorship
• Email sending

This helps maintain accountability across the team.

​

Permission changes

When roles change:

• Previous actions retain original attribution
• New permissions take effect immediately
• No retroactive access granted

​

Special considerations

​

Leaving the firm

When team members depart:

1. Change their role to read-only (if they need temporary access)
2. Remove them completely when ready
3. Reassign their tasks and responsibilities

​

Multiple advisors

For books with multiple advisors:

• Each advisor typically has member or admin access
• Consider who needs settings access vs. day-to-day access
• Use task assignments to manage workload distribution

​

Compliance requirements

If your firm has compliance requirements:

• Consider read-only access for compliance officers
• Document permission decisions
• Review access periodically

​

Troubleshooting

​

User can’t perform an action

Check:

• Their assigned role
• Whether the action requires admin access
• If there are any book-wide restrictions

​

Admin missing settings access

Possible causes:

• Browser caching old permissions
• Role change not saved properly

Fix: Have the user log out and back in, verify role is correctly set.

​

Principal needs to change

To transfer book ownership:

• Contact Slant support
• This is a special operation that requires verification

​

Next steps