From 4ad652a79d30e977bab0e912feb487746e87fc34 Mon Sep 17 00:00:00 2001 From: Prajwal214 <167504578+Prajwal214@users.noreply.github.com> Date: Fri, 26 Jul 2024 11:25:13 +0530 Subject: [PATCH] Doc: Updated Teams Typo in Docs (#17172) Co-authored-by: Prajwal Pandit --- .../admin-guide/roles-policies/use-cases.md | 43 +------------------ .../schemas/entity/teams/persona.md | 2 +- .../admin-guide/roles-policies/use-cases.md | 41 ------------------ .../schemas/entity/teams/persona.md | 2 +- 4 files changed, 3 insertions(+), 85 deletions(-) diff --git a/openmetadata-docs/content/v1.4.x/how-to-guides/admin-guide/roles-policies/use-cases.md b/openmetadata-docs/content/v1.4.x/how-to-guides/admin-guide/roles-policies/use-cases.md index a118195d042..f5e08535f0f 100644 --- a/openmetadata-docs/content/v1.4.x/how-to-guides/admin-guide/roles-policies/use-cases.md +++ b/openmetadata-docs/content/v1.4.x/how-to-guides/admin-guide/roles-policies/use-cases.md @@ -61,45 +61,4 @@ alt="PII Sensitive Tag Policy" caption="PII Sensitive Tag Policy" /%} -In this rule, we are specifying to deny operations if the table tag contains PII.Sensitive tag and if the logged-in user is not the owner, or their team is not the owner of the Table. - -### Use Case 5: Restrict User Account Access to a Specific Service/Database - -To restrict a user account to only see data from one specific service/database, you can create a policy that includes rules to allow access to the desired service and deny access to others. This involves setting up policies with specific conditions based on the service name. The following steps outline how this can be done using the API: - -1. **Create a Policy**: Define a policy that allows access to the specific service. -2. **Assign the Policy**: Assign this policy to the user or role. - -## Example Policy: - -```json -{ - "name": "ServiceAccessPolicy", - "rules": [ - { - "name": "AllowSpecificService", - "resource": "DatabaseService", - "operation": "View", - "condition": { - "match": { - "service.name": "desired_service_name" - } - }, - "effect": "Allow" - }, - { - "name": "DenyOtherServices", - "resource": "DatabaseService", - "operation": "View", - "condition": { - "notMatch": { - "service.name": "desired_service_name" - } - }, - "effect": "Deny" - } - ] -} -``` - -By implementing this policy, the user account will be restricted to access only the specified service, enhancing data security and ensuring that users can only view the data they are authorised to see. \ No newline at end of file +In this rule, we are specifying to deny operations if the table tag contains PII.Sensitive tag and if the logged-in user is not the owner, or their team is not the owner of the Table. \ No newline at end of file diff --git a/openmetadata-docs/content/v1.4.x/main-concepts/metadata-standard/schemas/entity/teams/persona.md b/openmetadata-docs/content/v1.4.x/main-concepts/metadata-standard/schemas/entity/teams/persona.md index 390d21c7307..4d647446271 100644 --- a/openmetadata-docs/content/v1.4.x/main-concepts/metadata-standard/schemas/entity/teams/persona.md +++ b/openmetadata-docs/content/v1.4.x/main-concepts/metadata-standard/schemas/entity/teams/persona.md @@ -3,7 +3,7 @@ title: persona slug: /main-concepts/metadata-standard/schemas/entity/teams/persona --- -# Team +# Persona *This schema defines the Persona entity. A `Persona` is a job function associated with a user. An Example, Data Engineer or Data Consumer is a Persona of a user in Metadata world.* diff --git a/openmetadata-docs/content/v1.5.x-SNAPSHOT/how-to-guides/admin-guide/roles-policies/use-cases.md b/openmetadata-docs/content/v1.5.x-SNAPSHOT/how-to-guides/admin-guide/roles-policies/use-cases.md index ca996b9824e..6839089ab52 100644 --- a/openmetadata-docs/content/v1.5.x-SNAPSHOT/how-to-guides/admin-guide/roles-policies/use-cases.md +++ b/openmetadata-docs/content/v1.5.x-SNAPSHOT/how-to-guides/admin-guide/roles-policies/use-cases.md @@ -62,44 +62,3 @@ caption="PII Sensitive Tag Policy" /%} In this rule, we are specifying to deny operations if the table tag contains PII.Sensitive tag and if the logged-in user is not the owner, or their team is not the owner of the Table. - -### Use Case 5: Restrict User Account Access to a Specific Service/Database - -To restrict a user account to only see data from one specific service/database, you can create a policy that includes rules to allow access to the desired service and deny access to others. This involves setting up policies with specific conditions based on the service name. The following steps outline how this can be done using the API: - -1. **Create a Policy**: Define a policy that allows access to the specific service. -2. **Assign the Policy**: Assign this policy to the user or role. - -## Example Policy: - -```json -{ - "name": "ServiceAccessPolicy", - "rules": [ - { - "name": "AllowSpecificService", - "resource": "DatabaseService", - "operation": "View", - "condition": { - "match": { - "service.name": "desired_service_name" - } - }, - "effect": "Allow" - }, - { - "name": "DenyOtherServices", - "resource": "DatabaseService", - "operation": "View", - "condition": { - "notMatch": { - "service.name": "desired_service_name" - } - }, - "effect": "Deny" - } - ] -} -``` - -By implementing this policy, the user account will be restricted to access only the specified service, enhancing data security and ensuring that users can only view the data they are authorised to see. \ No newline at end of file diff --git a/openmetadata-docs/content/v1.5.x-SNAPSHOT/main-concepts/metadata-standard/schemas/entity/teams/persona.md b/openmetadata-docs/content/v1.5.x-SNAPSHOT/main-concepts/metadata-standard/schemas/entity/teams/persona.md index 390d21c7307..4d647446271 100644 --- a/openmetadata-docs/content/v1.5.x-SNAPSHOT/main-concepts/metadata-standard/schemas/entity/teams/persona.md +++ b/openmetadata-docs/content/v1.5.x-SNAPSHOT/main-concepts/metadata-standard/schemas/entity/teams/persona.md @@ -3,7 +3,7 @@ title: persona slug: /main-concepts/metadata-standard/schemas/entity/teams/persona --- -# Team +# Persona *This schema defines the Persona entity. A `Persona` is a job function associated with a user. An Example, Data Engineer or Data Consumer is a Persona of a user in Metadata world.*