How to hide Promotions in Oracle ATG business control center without deleting them from the dcs_promotion table. Do we have some property where we can change it and make specific promotions unsearchable in business control center? I can not find anything yet where we can hide the promotions without deleting them. Need Help!
I'm new to ATG
The BCC allows access rights to be configured for all parts. I would recommend setting up folders in the BCC and restrict access to the folders. Below is an example of the access rights you can set:
Related
I want to make an EA-Project where I and some other people can see all information but some others should only see selected information.
Is it possible to create an EA-Project and do some settings so some defined elements or tags or element information are shown or hidden to defined users?
Or do i have to create two seperate EA-Projects?
No, that is not possible, if a user has access to an element, he has access to all its properties.
What you can do is hide parts of the model. There are two options:
Hide Project Root
You can use a group lock to hide a project root from users outside of that group. This is mainly a usability feature as it doesn't prevent users from accessing the contents of the hidden project root in other ways.
From the manual:
When you set a Group Lock on a Root Node, you can also select a checkbox to hide the Package in the Browser window from users who are not members of the locking group or Administrators. If you change the type of lock, or remove the lock altogether, the Package becomes visible to all users.
This feature hides the Root Package and its contents from initial view in the Browser window. It does not prevent the contents of the Package from being exposed in Model Searches. If you want to completely hide a Package from groups of users, consider Pro Cloud Server Visibility Levels.
Pro Cloud Server Visibility Levels
This is the real thing. It uses database row level security to prevent certain users from seeing the information stored in these rows. You'll need Pro Cloud Server to setup these visibility levels.
See the manual for more information
My company is moving to DevOps and Azure Boards from our previous environment in JIRA and we've encountered a very big issue with permissions.
At the moment, we have configured various Areas to support our development teams; we also have an Area dedicated to the Product team, where business requirements are first input and then reviewed. Each team has permission to edit work items in its own Area and it can't edit work items in other areas.
So, basically this is our structure:
Engineering: the main Area of the project; only administrators can edit work items
Engineering\Mobile: child area for the Mobile team; only members of the Mobile team and administrators can edit work items
Engineering\Backend: child area for the Backend team; only members of the Backend team and administrators can edit work items
Engineering\Device: child area for the Device team; only members of the Device team and administrators can edit work items
Engineering\Product: child area to review business requirements that are then moved to the appropriate area; everybody can edit work items
Now we're trying to give anybody from any team the permission to comment (aka. use the "Discussion" section) a work item regardless of the Area where it is, but it looks like the ability to comment is strictly related to the permission of editing the work item… In other words, we haven't been able to enable the Discussion section without giving the permission to edit a work item, which isn't ideal.
Is there a way to enable the Discussion section for anybody while keeping editing restricted?
Unfortunately, it's not able to do this in Azure DevOps at present.
Unless you give the users permission "edit work items in node" permission, otherwise he will not be able to comment in the discussion field separately.
There is already a user voice here--Add support for for/not rules in the inherited process model
According to our PM's reply:
We currently do not have any plans enable field level security. But we
will continue to track this suggestion. If we begin to see more votes
we will take it under further consideration.
You could vote that ticket and track the process. Sorry for any inconvenience.
I can't figure out if it possible and how it can be done to allow certain users in a Visual Studio Team Services project to see only the work items they created, instead of them all.
Thanks in advance for all your help.
For now, there is no ways to set permissions for a user to only view work items which were created by oneself.
It's only available to set permission based on Iterations and Areas for now.
But there has an user voice field level security permissions which suggest similar feature, you can vote and follow up.
And the features in below two user voices have already added in our backlog, when the features are archeived, it can also benefit the situation you met:
Hide Work Item Types (WITs) based on permission/security group
Add ability to hide/mask fields in a work item based on security/permissions
This is not supported. It used to be in the on-prem product a long time ago in the "Work item only view", but that has been removed in favour of the Stakeholder view.
I have a bunch of custom user groups. I need to change the permissions for one of the user groups so they don't see "Turn editing on" button or link. I figured out a way to do this in a reports section. I can't figure out a way to do this for course section.
I deactivated manage blocks and manage activities and that removed the button on all of the sections except courses. I tried to deactivate update course and a bunch other course related capabilities with no luck. Did not see any sort of manage courses capability.
Any help would be appreciated as I just inherited this site and have had no previous experience with Moodle.
Totara version 2.7
Moodle version 2.2.11
Do you want to this by code or configuration? If you want to do this, simply by configuration, just make a new user group for them "Site administration->User->Permissions->Define Roles", give them the ones you want them to have. Then assign the users in question this role. They should not see the buttons in question.
I am pretty new in Typo3 (I came from Joomla and WordPress) and reading the documentation I have some doubts related to the user manage the user in this CMS:
I am using Typo3 6.1.1 and reading here it seems to me that the user managment is quite different (maybe the documentation is related to an old version of the CMS?): http://docs.typo3.org/typo3cms/GettingStartedTutorial/EditAndCreatePagesAndContent/CreateUsersGroups/Index.html
In particular I am not understanding if in the 6.1.1 the backend user can ben divided in groups or if they simply are backend user because if I go into: ADMIN TOOLS ---> Backend User I can see the backend user but not the groups, why?
Tnx
Andrea
As you can see in mentioned doc, BE users can be divided by groups and easiest way for creating BE groups and next BE users is using WEB > List module.
Just using workflow showed at screen of this section you need to create records of both types (blue arrows) on the highest page (with id 0 - on screenshot it's called New TYPO3 site)
I'm not quite sure about the reason, but Backend User module doesn't allow to manage BE groups directly, however there's a tip (which is general for whole TYPO3) - you can create a BE group ad hoc - during the process of creating BE user by using additional icons in the form, take a look to screenshot below, the yellow pencil and black plus allows you to edit/create related records without canceling current edition.