In SAP BTP, managing teams effectively is crucial for restricting access to specific environments and ensuring that users only see and interact with the data and functions that are relevant to their roles. This lesson focuses on configuring reader and writer teams within runtime environments and understanding how these roles interact with broader application restrictions.
Introduction to Managed Teams
Purpose:
Controlled Access: Manage teams to define and restrict who can read from and write to specific environments.
Team Restrictions: Use teams to enforce access policies and maintain security within your SAP BTP applications.
Key Concepts
Reader Team: Users assigned to this team can only view (read) data and configurations.
Writer Team: Users assigned to this team can create, edit, and delete (write) data and configurations.
Environment Restriction via Reader and Writer Teams.
Runtime Environments
Requirement: Reader and writer team restrictions only apply to runtime environments.
Configuration Steps: You must create and activate a runtime environment before assigning reader and writer teams.
Example Scenario: Demo Environment Setup
Create and Activate Environment
Demo Environment: Let's consider a runtime environment called Demo Environment One.
Activation: Ensure that this environment is activated to apply team restrictions.
Define Teams:
Demo Reader One: A team is restricted to viewing (reading) the environment.
Demo Writer One: A team is granted permissions to modify (write) within the environment.