{"id":2321,"date":"2017-08-25T09:09:11","date_gmt":"2017-08-25T08:09:11","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=2321"},"modified":"2022-08-23T15:29:22","modified_gmt":"2022-08-23T14:29:22","slug":"skill-based-access-category","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/skill-based-access-category\/","title":{"rendered":"Skill Based Access of a Category"},"content":{"rendered":"

If you require only some users to be able to make a change to a category<\/em> or categories<\/em>, then you can use a skill<\/em> to stop other users from accessing it but they will still be able to see the options set.<\/p>\n

Setting the skill on a category<\/h2>\n

In Project Setup<\/strong>, select the Item Type<\/em> the category is set for. With the Assign Categories<\/strong> dialog open, select the category you wish to restrict. There is a \u2018Required skill<\/em>:\u2019 option which can be set differently for each category <\/em>in each item type<\/em>. This means that a category can be used Requirements<\/em> and SYSTEM REQ<\/em>s but have different skills for each item type and so can be altered by different users.<\/p>\n

\"Use
Setting a skill for a category to restrict access<\/figcaption><\/figure>\n

Once Project Setup<\/strong> is Saved<\/em> and Closed<\/em> any users that now login,<\/em> that do not have the required, will be able to see the option set but not alter it.<\/p>\n

Using the DEMO<\/em> project as an example, I set the category skill for Req Priority<\/em> to REQUIREMENT<\/em>. The ADMIN<\/em> user does not have the REQUIREMENT<\/em> skill and so once set, is able to see the as option set but not able to alter it.<\/p>\n

\"No
No access for this user<\/figcaption><\/figure>\n

When logged in as REQMAN<\/em> who does have the REQUIREMENT<\/em> skill, they can see and alter the category option.<\/p>\n

\"User
User has access<\/figcaption><\/figure>\n

This restriction works throughout WorkBench<\/em> including in queries, forms and Item Properties<\/em>.<\/p>\n

This also works in Web Access<\/em> forms<\/em> and queries<\/em>.<\/p>\n

Setting Categories in Project Setup<\/a><\/p>\n