{"id":2737,"date":"2014-11-17T13:05:45","date_gmt":"2014-11-17T13:05:45","guid":{"rendered":"https:\/\/www.cmwlab.com\/blog\/?p=2737"},"modified":"2026-02-13T06:35:59","modified_gmt":"2026-02-13T06:35:59","slug":"managing-dynamic-permissions-comindware-tracker","status":"publish","type":"post","link":"https:\/\/www.cmwlab.com\/blog\/managing-dynamic-permissions-comindware-tracker\/","title":{"rendered":"Managing dynamic permissions in Comindware Tracker"},"content":{"rendered":"

Managing complex workflows that involve people from different teams, departments and even locations often introduces unique challenges in the context of grouping and isolating your requests from each other dynamically, based on the request type, current workflow step and\/or other data points. If you have hundreds of requests fired off to your team every day, you may need to have specific people supervise requests of different types.<\/p>\r\n\r\n\"CMW<\/a>\r\n\r\n \r\n

For example, let\u2019s say you have two offices in two countries. The first team deals with US clients while the second team drills into the European market. You also have two managers supervising the process in each office and thus you have a question you need an answer for: how can you make each manager monitor his own team\u2019s requests only when all of them are running in the same system? This task is not a complicated one if you have Comindware Tracker<\/a> in place.<\/p>\r\n \r\n

You could go for creating separate \u201ccontainers\u201d for requests in different locations but what if you have other context-specific data points you want to use for filtering (e.g. request type, priority etc.)? The number of your containers will grow exponentially and the system will become unusable and non-maintainable at the blink of an eye. There is a more elegant (and time-saving) solution for that. Comindware Tracker<\/a> lets you set user roles and permissions contextually, based on data you have in each particular request. That means you can make US requests with \u201cCritical\u201d priority visible to one manager, requests from Europe with \u201cMedium\u201d priority to another. Any combination of factors can be used to define view\/edit\/assignment permissions, while all of your requests logically reside all in one place.<\/p>\r\n \r\n\r\n\"Managing<\/a>\r\n

Setting that up is also very easy \u2013 you just need to have all of your data fields you will use for filtering (e.g. request region, priority etc.) in your request form, then map those fields\u2019 values to the corresponding users\/user groups through calculating them in separate fields, and then add those user fields to corresponding workflow roles. When done, the system will automatically calculate all of the permissions dynamically and your managers will see the requests they are supposed to only, without having to set up any complicated lists and messing with different request \u201cfolders\u201d.<\/p>\r\n \r\n

This is one of the unique features of Comindware Tracker and once again, you won\u2019t need a developer to set that up.<\/p>\r\n

\n
\n