Skip to content

Commit 4551f94

Browse files
authored
Merge pull request #10681 from harness/tag-based-access-control
Manage Access Control for Connectors
2 parents 283cecd + bdbd893 commit 4551f94

File tree

8 files changed

+60
-0
lines changed

8 files changed

+60
-0
lines changed
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: Manage Access Control for Connectors
3+
description: Learn how to manage access control for connectors by type, name, or tags.
4+
sidebar_position: 39
5+
helpdocs_topic_id: uzzjd4fy67
6+
helpdocs_category_id: w4rzhnf27d
7+
helpdocs_is_private: false
8+
helpdocs_is_published: true
9+
---
10+
11+
[Role-based access control (RBAC)](https://developer.harness.io/docs/platform/role-based-access-control/rbac-in-harness) in Harness lets you control who can access your resources, what actions they can perform, and where they can do it. Access is based on roles assigned to users, user groups, and service accounts.
12+
13+
### Configure Roles
14+
15+
1. Navigate to Account Settings → Access Control → Roles.
16+
17+
2. [Add or edit a role](/docs/platform/role-based-access-control/add-manage-roles.md), check for Shared Resources → Connectors section to ensure the appropriate permissions are granted, as shown in the image below.
18+
19+
![connector-roles](./static/connector-role.png)
20+
21+
### Configure Resource Groups
22+
23+
1. Go to Account Settings → Access Control → Resource Groups, and [create or edit a resource group](/docs/platform/role-based-access-control/add-resource-groups.md).
24+
25+
2. Select the appropriate Resource Scope based on your requirements, and set Resource to All if you want to provide access to all resources. Otherwise, select Specified, as shown below.
26+
27+
![resource-group-and-resource](./static/resource-group.png)
28+
29+
3. After specifying the Resources, search for Shared Resources and select Connectors. While creating a resource group, the connectors can be added in the following four ways:
30+
31+
* **All**: Provides access to all connectors at a particular resource scope.
32+
33+
![connector-all](./static/all-type.png)
34+
35+
* **By Type**: Grants access to one or more specific connector types, such as artifact repositories, cloud providers, secret managers, and more, based on your selection.
36+
37+
![by-type](./static/by-type.gif)
38+
39+
* **By Tag**: Grants access to connectors based on matching tags. If a connector has a tag included in the resource group's tag list, users with the corresponding role assignments automatically gain access.
40+
41+
If the tag is removed from the connector, access is automatically revoked.
42+
43+
![by-tags](./static/by-tags.gif)
44+
45+
* **Specified**: Grants access to one or more specific connectors that have already been created. This option is available only at Account-only, Organization-only, or Project-only scopes.
46+
47+
![specified](./static/specified.gif)
48+
49+
By following these steps, you can enable users to manage access control for connector in four different ways through their assigned resource groups, allowing for more granular access control.
50+
51+
### Assign access control for connectors
52+
53+
After configuring the resource group for connectors, you need to assign the [role binding to a principal](/docs/platform/role-based-access-control/rbac-in-harness/#principals).
54+
55+
For example, to assign access to a user, navigate to Account Settings → Access Control → Users. For the relevant user, click on Manage Role Binding, and then select the Role and Resource Group created above.
56+
57+
![manage-role](./static/role-binding.png)
58+
59+
60+
50.1 KB
Loading
213 KB
Loading
267 KB
Loading
Loading
Loading
93.8 KB
Loading
1.21 MB
Loading

0 commit comments

Comments
 (0)