User Tags

Modified on Wed, 17 Aug 2022 at 04:12 PM

What are tags?

Tags are 'flags' tied to a user profile to assist with reporting and special use cases. Tags can also be utilized to separate groups of users based on platform access, location, notifications, and regulations. Care360 can accommodate all users with varying needs by tagging profiles to restrict certain features or enforce specific workflows for parts of the software.

How can tags be added to a user?

Generally, tags are added to users via a census file (initial data import carried out during the implementation process). The census file will be configured with all necessary tags tied to each user, and specific rules for each tag are then configured.

If the need arises to add a tag to a few users after the census file import, new tags can be added to any user profile via the admin dashboard.

What are admin tags?

Admin tags are applied to an admin profile to restrict visibility of other users and allow them to only see users with matching tags under the Manage>Employees tab. An admin without admin tags can view all users that exist on the platform within their organization. Admin tags can also be used to restrict access to certain processes that would normally be available to an admin level account.

Are admin tags required?

No, admin tags are not required to use Care360 as an admin level user, although helpful in some use cases. Admins without an admin tag have the ability to view all users in the organization, so certain actions may be more time consuming without the filtering provided by the feature depending on organization size, region count, and management/data hierarchies.

What are some common use cases with tags?

A large portion of the tagging process is utilized to filter users into various groups that will follow different workflows/guidelines. Additionally, tags can be used to categorize users by fields such as work location, notification type, testing schedule, etc. The tagging system can be configured to be as high level as 'region' or as granular as 'office room number' all at the same time.

Below outlines some common examples for tagging, and how they will effect the end user workflow. Please note that these functions will have a tag assigned to them, and all users with the matching tag will abide by the rule specified by the override:

Disable Test Result Reporting: Users with this tag are not required to submit test results to maintain a green passport.

Disable Vaccination: Users with this tag do not need to provide proof of vaccination.

Test Order Link: Allows this user to order test via a custom typeform link on their user profile.

Testing Type: Disable native test reporting, allow for a custom testing link.

In addition, many things in the system can be configured on the back end to function differently for tagged users such as the data consent displayed for users overseas, the testing frequency/Quarantine duration for a certain population of users, or the permissions their Admin role may have access to.

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 atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article