Teams
As a Braze admin, you can group your dashboard users into Teams with varying user roles and permissions. 이렇게 하면 편집할 수 있는 콘텐츠 유형을 분리하여 서로 관련이 없는 여러 대시보드 사용자 그룹이 하나의 작업 공간에서 함께 작업할 수 있습니다.
Teams can be set up across customer base location, language, and custom attributes so that Team members and non-Team members have different access to messaging features and customer data. 다양한 참여 도구에서 팀 필터와 태그를 할당할 수 있습니다.
모든 Braze 계약에서 팀을 사용할 수 있는 것은 아닙니다. 이 기능을 이용하고 싶으시면 Braze 계정 매니저에게 문의하거나 상담을 요청하세요.
How do Teams differ from permission sets and roles?
You can use Teams, permission sets, and user roles to manage dashboard user access and responsibilities within Braze. Each feature encompasses a different collection of permissions and access-controls.
Key differences
At a high level, each feature has a different scope:
- Permission sets control what dashboard users can do across all workspaces.
- Roles control what dashboard users can do in specific workspaces.
- Teams control the audiences that dashboard users can reach with their messages.
Feature | What you can do | Scope of access |
---|---|---|
Permission sets | Bundle permissions related to specific subject areas or actions (such as for “Developers” and “Marketers”), then apply them to dashboard users who need the same permissions across different workspaces. | Company wide |
Roles | Bundle individual custom permissions and workspace-access controls (such as “Marketer - Fashion Brands”, where the user has certain permissions associated with their role as a marketer and is limited to the “Fashion Brands” workspaces). Then assign a role to dashboard users to directly grant them the associated permissions and workspace access. Users with this level of access are typically managers in more tightly controlled setups with many brands or regional workspaces in one dashboard. |
Specific workspaces |
Teams | Limit dashboard user access to resources based on the audience (such as customer base location, language, and custom attributes). Users with this level of access typically are responsible for a specific scope within the brand that they’re working on, such as building language-specific content for a multilingual brand. |
Specific dashboard |
Creating Teams
설정 > 내부 팀으로 이동하여 팀 추가를 선택합니다.
팀 이름을 입력합니다. If desired, use the Define Team field to select a custom attribute, location, or language to further define what user data the Team has access to. For example, a possible use case is to perform testing with Teams by creating a development Team that only has access to test users, identified by a custom attribute. 또 다른 사용 사례는 제품에 따라 사용자와의 커뮤니케이션을 제한하는 것입니다.
If a Team is defined by a custom attribute, language, or country, you can then use the Team to filter end-users for features like campaigns, Canvases, Content Cards, segments, and more. For more, see Assigning Team tags.
Assigning users to Teams
Braze administrators and limited users with the company-level permission “Can Manage Company Settings” can assign Team-level permissions to a dashboard user with limited access. When assigned to a Team, dashboard users are limited to only read or write data available to their particular Teams, such as user language, location, or custom attribute, as defined when the Team was created.
To assign a user to a Team, navigate to Settings > Company Users and select a user you’d like to add to your Team.
그런 다음 다음 단계를 수행합니다:
- 편집을 선택합니다.
- 사용자 역할을 제한으로 설정합니다.
- 적절한 작업 공간에 추가합니다.
- 이 사용자를 추가하려는 팀을 선택하고 팀 권한 열에서 특정 권한을 할당합니다.
Available Team-level permissions
The following are all available permissions you can assign at the Team level. 여기에 나열되지 않은 모든 권한은 작업 영역 수준에서만 부여되며 이러한 권한은 Teams 권한 열에 “–“으로 표시됩니다.
- 캠페인, 캔버스, 카드, 콘텐츠 블록, 기능 플래그, 세그먼트, 미디어 라이브러리 및 환경설정 센터에 액세스합니다.
- 캠페인, 캔버스 발송
- 카드 게시
- 세그먼트 편집
- 사용자 데이터 내보내기
- 사용자 프로필 PII 준수사항 보기
- 대시보드 사용자 관리
- 미디어 라이브러리 자산 관리
각 사용자 권한에 포함된 항목과 사용 방법에 대한 설명을 보려면 사용자 권한 섹션을 참조하세요.
Assigning Team tags
You can assign a Team to Canvases, campaigns, cards, segments, email templates, and media library assets with the Add Team filter.
- Based on the definitions applied when the Team was created, when a Team filter is assigned, that engagement tool’s audience is restricted to user profiles that match the definition.
- Based on assigned permissions, Team members will only be allowed to access dashboard engagement tools that have their Team filter set. If they have limited or no workspace permissions, they must add a Team filter to certain objects before they can save or launch them. Team members are also able to filter Canvases, campaigns, cards, and segments by Team to identify content relevant to them.
사용 사례
다음 두 가지 시나리오는 Braze의 마케터 미셸의 경우를 가정한 것입니다. Michelle is a member of a Team called “Development”. She has access to all of the Team-level permissions for the Development Team.
In this scenario, Michelle is still a member of the Development Team, but she also has an additional workspace-level permission.
Because Michelle has the workspace-level permission of “Access Campaigns, Canvases, Cards, Content Blocks, Feature Flags, Segments, Media Library, and Preference Centers”, she can view and assign other Team filters to the campaign she creates.
Similar to the first scenario, Michelle must add the Development Team tag to the campaign before she can launch it.
Testing with Teams
One possible use case for Teams is to create a Teams-based approval system for testing and launching content in a production environment.
To do so, create a “Development” Team that only has access to test users. You can limit a Team to only access test users if your test users are identifiable by a custom attribute. Then, add the custom attribute as a definition when creating or editing the Team (see the preceding section Creating Teams). 승인자는 모든 사용자에 대한 액세스 권한이 있어야 합니다.
일반적인 프로세스는 다음과 같습니다:
- The Development Team creates a campaign and adds the “Development” Team tag.
- The Development Team launches the campaign to test users.
- The Approver Team validates the local campaign design, promotes, and launches. To launch, the Approver Team changes the Team tag from “Development” to “[All Teams]” and relaunches the campaign.
활성 캠페인에 대한 변경 사항:
- The Development Team clones the running campaign, adds the “Development” Team tag, and saves.
- The Development Team makes edits and shares with the Approver Team.
- The Approver Team removes the “Development” Team tag, pauses the previous campaign, and launches the new campaign.
Archiving an existing Team
You can archive Teams from the Internal Teams page.
Select one or many Teams to archive. If the Team is not associated with any object within Braze, the Team will be archived immediately. If the Team is associated with an object, you will be presented with an option to remove the Team after the archive process or replace the Team.
Braze admins can unarchive a Team by selecting the archived Team and selecting Unarchive.