Profile Settings for Outreach Meetings

Created by Aye Myat, Modified on Mon, 9 Feb at 11:02 PM by Alsabana Sahubarali

Purpose: 

The purpose of this article is to provide direction to Outreach Admins in configuring profile settings for Outreach Meetings. 

Outreach Admins have the ability to allow or deny certain Outreach users from accessing features of Outreach Meetings.

Intended Audience: 

  • Outreach Admins

Adjusting Profile Settings

  1. Click on Administration on the left navigation menu to access the Administration settings for your instance.
  2. Underneath the Users & permissions 
  3. Select the profile of the group of users you'd like to adjust settings for.
  4. Under the profile settings, there is a section called Meetings in which you can control what permissions. These include:
    • The ability to schedule meetings
    • Meeting Type Create/Share Permissions
    • Meeting and Meeting Type visibility

The settings above are described below:

 

Can view meeting records

This setting controls what meetings users of this profile can see:

  • Owned by them - Users will only see their own meetings
  • Owned by them and their reports - Users will only see their own meetings and the meetings of their reports (determined by governance roles)
  • Owned by anyone - Users will see all meetings
Can view private meeting types

This settings controls what meeting types users of this profile can see:

  • Owned by them - Users will only see their own created meetings types
  • Owned by them and their reports - Users will only see their own created meetings types and the created meetings types of their reports (determined by governance roles)
  • Owned by anyone - Users will see all meetings types

 

Additional Information

For guidance on managing calendar permissions for Outreach meetings, see How to Manage Outreach Meetings Calendar Event Visibility.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article