Tips & Tricks - Tailoring Users and User Roles in SectyrHub 340B

Created by Ben Fredricks, Modified on Sat, Dec 28, 2024 at 9:37 PM by Ben Fredricks

 November 26, 2019

Hi,

Every organization is comprised of specialized professionals who execute specific roles. SectyrHub 340B enables your organization to increase collaboration while maintaining necessary constraints by tailoring permissions and levels of access to the user. 

Please Note: Only users with admin rights can add new users and tailor their roles. Not an admin user? Check out our feature enhancements below! 

 

 

Did you know...

1. Each user is given a user role that is entirely customizable.

The role determines what actions/permissions the user will have within the solution. This can be expansive to allow the user to access all features and workflows, or they can be detailed to limit the user. When roles are created, you can determine what the user can see and what the user can edit.

Many users will likely have view/edit access to all sections (full access) while others may have the ability to view everything and edit nothing (view only). However, if you have an employee that works solely with audits for example, a role can be created to give them access to the audit workflows only.

2. Each user can receive access to all covered entities (the System), a selected sub-set of covered entities, or a single covered entity. 

The level of access determines what covered entity dashboards the user will have available to them. Providing access to the System dashboard will allow for the greatest level of oversight, as the users at the System level will be able to drill down into all covered entity dashboards. To provide access to more than one covered entity, simply add the users at each covered entity dashboard that is included within their scope of responsibilities.  

Pro Tip: If a user needs different permissions at different entities, that can be done as well! Example: A user is set up at CE 1 with full access and CE 2 with view only access.

 

Organization Oversight - The System Perspective 

As the number of SectyrHub 340B™ users at your organization continues to grow, your System admin users can manage everyone from the System admin settings.

On the System dashboard, click the blue pencil icon next to your organization’s name to access the admin settings. The second tab, All System Users, displays everyone who has access within your System and includes their emails, joined date, last logon date, and their roles and levels of access. Removing users from this tab will remove their access throughout the solution.

 
 
Compliance Insight - Bringing in External Auditors

Your organization may decide to give temporary limited access to third parties. Interested in having an auditor come in to do an integrity audit of your covered entity? Give them view only access so they can access documentation, then remove their access once completed.

 
Planned Enhancement - User Specific Dashboards!

With an estimated release on Tuesday December 3rd, SectyrHub 340B™ will feature a new dashboard that rolls up all covered entities specific to a user into a single location, providing additional oversight for users with access to more than one covered entity. This user dashboard has the same basic layout as the System dashboard, with color-coded statuses and audit tables.

 
 
Login to SectyrHub 340B™
 

Want to learn more?

Our HelpDesk is full of helpful articles.
Here are a few links related to Users and User Roles:

Category: Users and User Roles
Video: Users and User Roles

 

View our HelpDesk articles
 

Happy Thanksgiving
from our family to yours.

We are thankful for the opportunity to be a part of your on-going 340B compliance journey.
We are all in this together!

 
Follow us on social media!
Facebook
Twitter
LinkedIn
Website
 

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