Tag: data

Data stored or administered within Cradle.

Topic including, control/access, import/export and manipulation.

Posted on

Skill Based Access of a Category

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

Setting the skill on a category

In Project Setup, select the Item Type the category is set for. With the Assign Categories dialog open, select the category you wish to restrict. There is a ‘Required skill:’ option which can be set differently for each category in each item type. This means that a category can be used Requirements and SYSTEM REQs but have different skills for each item type and so can be altered by different users.

Use a skill to restrict access
Setting a skill for a category to restrict access

Once Project Setup is Saved and Closed any users that now login, that do not have the required, will be able to see the option set but not alter it.

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

No skill, so no access
No access for this user

When logged in as REQMAN who does have the REQUIREMENT skill, they can see and alter the category option.

User has skill to has access
User has access

This restriction works throughout WorkBench including in queries, forms and Item Properties.

This also works in Web Access forms and queries.

Setting Categories in Project Setup

Posted on

Skills Based Access of Items

When not everything can be shared

Imagine you have a project and teams of people working on it. You can control who sees what by placing staff in different teams (for information watch this video about collaborative teams). You can provide skills based access to individual frames within the item. However, there maybe one type of item which only certain team members can see, maybe a Finance item. The solution is to set a skill for the item type. Ensure those who are allowed to view the item type have the skill.  For those assigned the required skill, all the other access controls still get applied, (CM status, security clearance and ownership).  For those without the skill, the item type disappears from existence, it is as if the project schema had not defined the item.

Project setup setting skills based item access
Skills Based Item Access
  1. Login to WorkBench as a user who can modify the schema
  2. Start Project Setup from the Project tab, set Options to User Settings and select the Skills tab
  3. Select New and define a new skill
  4. Set Options to Item Definitions and select the Item Types tab
  5. Select the item type to be controlled and choose the new skill from the Required skill: drop-down list
  6. Save the schema and close Project Setup
  7. From the Project tab, select User Setup and for each user who is to be able to see the item type, select that user, select Skills, add the new skill to the user’s user profile and save the profile

RO Skill Based Access Feature

New Cradle-7.2

Now imagine the scenario that you want team members to see an item type but you don’t want them to be able to change any aspect of it. The latest version of Cradle allows you to set Read-only access for these item types.

Skill based access levels for items
Skill Based Access Levels for Items
Related Items

To restrict access to categories alone, this article will help.

https://www.threesl.com/blog/skill-based-access-category-users/