How to add and assign tags within your service

Tags can be added and managed in the Service dashboard, only available to our business users and accessible through https://calendar42.com/accounts/management/.

Tags are typically useful to specify details that characterise or identify users (or groups of users) or that are shared between users (or groups of users). Although we can’t possibly think of every single useful application of tags in services, we have listed some helpful tips for how to use and define them.

Adding a tag

  1. Go to your service dashboard, select your service and select the tags page. This page contains the tags available in your service and the users associated with them.
  2. Click the '+ Add a tag' button to add a new tag. Enter the name of the tag and press 'Add tag'. Note that you can not change the name afterwards, so make sure to double check it.

Your tag is now created and you can start assigning it to people.

Assigning tags

The easiest way to assign tags is by adding it to the user on the user detail page itself.

  1. Go to your service dashboard, select your service, click 'users' in the main navigation and select the user you want to add the tag to.
  2. Click the 'Add tags' button and use the checkboxes to select on or multiple tags.
  3. Click 'Add tags' again to add them to the user.

Removing tags from a user

It's not possible to remove tags entirely from the service, though you can remove the tags from users.

  1. Go to your service dashboard, select your service, click 'users' in the main navigation and select the user you want to add the tag to.
  2. Go to the tag section on the user detail page, located on the right.
  3. Hover over the tag you want to remove for a cross to appear. Click the cross to remove the tag from the user.

What makes up a good tag?

  • A valid tag is no alias of one person
  • A valid tag is not too generic (i.e. applicable to all users in service)
  • A valid tag ideally contains no spaces (as we don't support smart search yet);
  • A valid tag ideally is not used for quantitative ranking (other methods like frequencies measured might be better utilised for this)
  • A valid tag ideally can be used as a part of a bigger query
  • A valid tag ideally does not have another tag as part of its name
  • A valid tag ideally does not have a one-on-one relation with another tag
  • A valid tag ideally does not require too frequent revising/management by a planner or administrator (e.g. years of experience, which would have to be updated per user annually)

Feedback and Knowledge Base