Managing Company User Permissions #

The Team module and user permissions serve two different purposes in Propel.

The Team module is designed primarily as a member directory and organizational chart. It allows you to organize people into departments and document information such as their roles and start dates.

User permissions are managed separately under Company Settings → Users.

Only Company Admins have access to these settings.

Company Users #

Under Company Settings → Users, you will see all active users who have access to the company instance.

There are two types of users:

• Company Admins
• Company Users

Company Admins have administrative access to the company instance, while Company Users can be given specific permissions based on their responsibilities.

Allow Company Users to Create Meetings #

Company Users can be given permission to create meeting series.

If a checkmark appears next to a Company User for meeting creation, that user has permission to create meetings.

This is especially useful for managers or team leaders who may need to create:

• Department meetings
• Team huddles
• One-on-one meetings

Meeting creation permissions can be managed under Company Settings → Users.

Manage Access to the Plan Module #

Company Users may also need different levels of access to the Plan module, which contains areas such as your strategy, health, and value information.

These permissions are managed directly within the Plan module.

Navigate to Plan and select Share in the upper-right corner. From here, you can manage which areas of the Plan each individual user can access.

If a user does not have access to a particular Plan tab, that tab will not appear when they view the Plan module.

For step-by-step instructions, see Sharing Permissions in the Plan Module in the Plan section of the Support Desk.

Remember: Team vs. Users #

The easiest way to think about the distinction is:

Team = who is part of the organization and how they are organized.

Company Settings → Users = who has access to the software and what they are permitted to do.

Keeping these functions separate allows you to build your organizational structure in the Team module while maintaining administrative control over software access and permissions.