I need to customize Grafana.
I have created 2 organization and some users.
I need to create some dashboards that will be visible to only one organization among the newly created organizations.
Log in as admin
Switch to the organization you want. In the documentation this organization is called current organization and changes will affect only this.
Add Data Sources
Add Dashboards
For other organizations/dashboards, repeat again steps 2-4.
Related
I would like to have a user in Azure Devops that only has access to review the test plans sections in Azure Devops. I don't want the users to be able to go to the Board area and make modifications.
I've attempted to make users in the different types (Basic, Basic + test plan) but they always have access to edit items on the board. I tried creating them as a stakeholder and that didn't work either.
The last things I tried was creating a group and denying access to everything except project info and test plans, but this didn't work either.Picture of Project setting for test plan group
Is there any other approach I can use?
If a user has access level(stakeholder, basic or basic + test plan), the user will has access to view the Board.
You could refer to this doc about Access Level.
But you could set the permission for the users to prevent them from modifying the work item.
You could go to Project Settings -> Project configuration -> Select the Area -> Security.
You could deny the Edit work items in this node or View work items in this node .
We have Jenkins installed and I'm wondering how to add an existing user to a Jenkins group.
I find how-to's for the case where in Configure Global Security the Security Realm is set to Jenkins' own user database. We have set this to Active Directory - but maybe this doesn't make a real difference to the problem.
In section Authorization we have set Matrix-based security and there are already four groups defined from a previous user, those groups have some custom rights set, and a bunch of AD users were added to those group somehow.
My problem: if I try to add a new user, I can add it to the matrix and give him the rights, but I don't see how to simply add the user to the group. I don't want a huge list of users who all have the same rights - I just want them bundled each into one of the four groups. But how can I add a user to a group? It was possible somehow before, as there are obviously users added to those groups.
Maybe a plugin was uninstalled by accident and is missing for this purpose? But I guess that in that case the Matrix-based security wouldn't even be displayed anymore!?
Any help? Thanks.
In this specific case the groups are AD groups and the users are added to those groups in the AD, not in Jenkins. So, if you have set the Security Realm to Active Directory you must add users to groups on the active directory level - not within Jenkins.
Is there a way to set up a personal dashboard for TFS that is in addition to the team dashboard?
We have a group of users who want to see different information than what is on the team dashboard, and would like their own dashboard/view to show things like Tasks Assigned to them, Open Backlog Items, etc. But this would only be for the individual (others want to see different queries and other widgets depending on their tasks in a team).
There are no personal dashboards at present. However, there are work item query tokens like #Me so you can have one query that is personalized for whoever is viewing the dashboard.
Yes, you can view all work items assigned to you in web based TFS
http://{TFS Server}/{ProjectsCollectionName}/_work
You will see your dashboard as attched screenshot
So here is my situation, I have an umbraco website which is divided into sections for each department in an organisation. Each organisation wishes to manage its own content and want their own admin. However they don't want the admins of other departmetns to be able to modify the content outside their own department.
Is there a way to restrict content writers to have access to edit content only in a specific part of the umbraco backend?
Yes, when creating the new user you can set the starting node of the Content and Media so he will be able to only modify those pages and their children
In addition to Eyescream's answer above, you can also set permissions for pages as well. If you right click on the node in the tree, and select "permissions" from the list of options, you can set permissions on specific actions for that node for each user as well. E.g. you can make it so that certain users cannot delete or move certain nodes.
I am having a little difficulty understanding when a person should configure JIRA permissions using groups and when they should use project roles. I have read the online documentation, however, the difference between the two seems subtle.
A group seems simple enough. Group users into a named bucket. Assign the group to one or more permissions within a permission scheme to enable access to functionality for any users within the group. Assign the permission scheme to a project to apply the permissions to that project.
A project role seems very similar. It does all of the above except that you can also add groups to project roles. It seems that a project role also allows a project administrator to add their own users to a project instead of requiring a system administrator.
However, I am not sure how I can leverage this. Here is an example of what I want to achieve.
Have multiple projects created in JIRA.
All of our managers, developers, etc. have the same permissions across all projects.
Our clients have access only to their projects.
I think that the best way to accomplish this is to:
Create an employees group to which I add all of our employees.
Create one or more project roles to which I add the appropriate clients.
Assign permissions to the Default Permissions Scheme using the employees group.
Copy the Default Permission Scheme to a new project specific scheme, e.g., client-scheme
Assign the client-scheme to the client specific project.
However, it seems that I am not leveraging project role membership. How does this come into play?
What is the best practice for using JIRA groups and project roles? What is the different between the two?
We are advising to work with roles as it has a couple of advantages
a. You can setup the complete configuration based on roles.
For instance you might have a workflow transition 'validated' which can only be executed by someone who is a tester.
You have the choice to add a transition condition 'user is in group tester' or 'user has the role tester'.
If you are working in an organisation where users have different roles in different projects, choosing the first transition condition (user is in group tester) will not work (or you would need a new workflow for each project)
The same applies for notifications.
You can configure a notification on the 'issue resolved' event, specifying that the 'users in group tester' get notified or 'users who have the role tester'.
When using roles, adding someone to a project is very simple - just check what role the person has in the project, add them in the project configuration (view members) and you are done. He will have the right permissions, get the right notifications ...
b. Configuration
When you use roles for configuration, you don't need system administration rights to add someone to a project. The project lead will be able to add the user. No need to bother the system admin.
Looking at your description, I would have
A project role 'employee'
A project role 'customer'
A group 'employees'
configure the project role such that the group employees is a default member of the project role employee
This way you can use the same permission scheme for all projects. When adding a new project, you just need to add the client specific userid to the client role.
When a new employee start, you add him to the employees group.
The day that you have a specific, ultra secret project, where only a couple of employees need to have access, you can remove the group 'employees' from the role 'employee' and add the specific users to the role.
Hope this helps
Francis
Historically, JIRA had groups first. Then roles came along and are the recommended way to control authorization in most cases.
~Matt
Groups are global. Roles can be thought of as per-project (local) groups.
Roles are much better: else with a large number of projects you quickly end up with a proliferation of Groups and permission schemes (one per project).
You lose nothing by using role-based permission schemes, since you can add a Group to a role.
But you gain a lot of flexibility. Eg you'd currently have the Employee role be filled with your Employees group for every project, but as your company and complexity grows, you can have different Employees per project, without having to change the permission schemes