This section refers to a deprecated version of the product. The new version is FE&R. To access FE&R, contact your CSM.
📘 To learn more, read the FE&R documentation.
LogoLogo
PlatformsPricingRessources
  • User documentation
  • Onboarding
  • Help Center
  • Release Notes
  • Flagship - Deprecated
  • Feature Experimentation & Rollout (ex-Flagship) is evolving!
  • GETTING STARTED
    • 👉Managing multiple environments
    • Using the trial version of Flagship
  • First steps with Flagship
    • Quick start guide
    • Glossary
  • Implementation
    • Sending transactions from the AB Tasty Shopify app directly to Feature Experimentation & Rollouts
  • Integrations
    • Heap Analytics integration (Push)
    • Tealium AudienceStream (receive audiences)
    • FullStory integration (segment exports)
    • Heap Analytics integration (Pull)
    • Google Analytics integration (pull audiences)
    • Segment Integration (receive traits)
    • Mixpanel integration (cohort exports)
    • 👉Retrieving your third-party tools’ audiences in AB Tasty - Feature Experimentation & Rollouts
    • Zapier integration
    • Segment integration
  • Steps configuration
    • 👉Configuring Sequential Testing Alerts
    • 👉Configuring your Flags
    • 👉Using the scheduler
    • 🛠️[Troubleshooting] How to target a large number of users at the same time?
    • 👉Configuring KPIs
    • 👉Using the automatic rollback option
    • 👉Targeting configuration
    • 👉Dynamic allocation
    • 👉Traffic allocation
  • Team
    • Access Rights, Teams & User Management
    • 👉Defining rights per project
  • DEMO
    • AB Tasty - Feature Experimentation & Rollouts Demo - How to use it
  • Navigating the interface
    • 👉Archiving use cases from the dashboard
    • 👉Flags page
    • 👉Running a search on the dashboard
    • Navigating the Flagship interface
  • REPORTING
    • 👉Verifying your hit setup
    • 👉Exporting reporting data
    • Understanding the "Chances to win" indicator
    • 🛠️[Troubleshooting] How can I know my test is reliable and my data significant enough to be analyzed?
    • Reporting - A/B Test
    • 👉Using the reporting filters
  • API keys & Settings
    • 👉Acting on your account remotely
    • 👉Using Experience Continuity
    • visitor experiment option
  • FEATURES SETUP
    • 👉Bucket allocation
  • SDKs integration
    • 👉Managing visitor consent
    • 👉Understanding the use of SDKs
  • FAQ
    • Can I make a comparison for each reporting?
    • Can I use Flagship even if my SDK stack is not available?
  • Platform integration
    • 👉Webhooks page
  • Decision API
    • Decision API for non-techie users
  • Account & Profile
    • 👉Configuring account restrictions with MFA
    • 👉Configuring a FA on your profile
  • RELEASE NOTES
    • October - Flagship becomes Feature Experimentation & Rollouts
    • February - Release Notes
    • 📅January - Release Notes
    • 🎉December - Release Notes 🎉
    • 🦃November - Release Notes
    • September Release Notes 🎨
    • June Release Notes 🐞
    • 🍸May Release Notes ☀️
    • Flagship Release Notes April 🐇
    • Flagship February release notes 🏂
    • Flagship January release notes 🎉
    • Flagship November release notes 🦃
    • Flagship October Release Notes 🎃
    • Flagship September Release note 🎒
    • Flagship August Release Notes 🐬
    • Flagship Release Notes July ☀️
    • Flagship Release notes June 🌻
    • Flagship Spring Release May 🌸
    • Flagship Release Notes: Fall
  • Use cases
    • 👉Duplicating a winning variation
    • 👉Configuring a Feature Toggle/Flag
    • 👉Configuring an A/B Test
    • 👉Configuring a Progressive rollout
    • 👉Configuring a Personalization
  • VIDEO TUTORIALS
    • [Video Tutorial] AB Test
    • [Video Tutorial] Feature Flag
    • [Video Tutorial] Progressive Deployment
Powered by GitBook
LogoLogo

AB Tasty Website

  • Home page AB Tasty
  • Blog
  • Sample size calculator
  • Release note

AB Tasty Plateform

  • Login

© Copyright 2025 AB Tasty, Inc, All rights reserved

On this page
  • 📖 Definition
  • ⚙️ Configuration
  • Edit Rights
  • User rights
  • ⚙️ Use case

Was this helpful?

Edit on GitLab
Export as PDF
  1. Team

Defining rights per project

📖 Definition

On your dashboard, you may have multiple projects or feature teams working on different projects. To avoid configuration mistakes, you can allow specific rights to specific users on each project.

⚙️ Configuration

On the dashboard, from each project line, you can click the 3 dots to open the “Edit Rights” panel.

Edit Rights

When you open “edit rights”, there is an administration panel where you find every user who can see and interact with your project.

In this interface, you can add, delete, or modify users of the project and for each environment.

You can define in that one place which user role they should have in each environment.

⚡️ Heads Up

When doing changes on project rights, don’t forget to save before closing the modal, otherwise, your changes will not be applied.

User rights

You can choose between 4 different types of user rights on your project rights panel:

From left to right:

  1. Viewer: Can only have a look at what’s happening on the project

  2. User: Can create/pause/delete/archive use cases inside the project

  3. Admin: Same rights as user role, in addition to managing users inside the project

  4. Blocked: The member will not have access to the project in this environment

⭐ Warning

A user can be added twice (either ad-hoc or through a team). The higher role of the user will be taken in priority. Ex: if the user is manually added as a Viewer and he's part of a team which is Admin, then he'll have Admin rights on the project.

⚙️ Use case

“As a member of a Product-&-Tech team with several feature teams or squads, I deeply need to organize my dashboard to let these teams see only the projects in their scopes.

Thus, for our e-commerce platform, I can create a project for the Home page, another for Product Pages, and another one for the Paywall. But, my 3 feature teams working on those 3 different scopes will only see the project(s) they have been added to.

…of course, as a Project Manager or upper role, I can still have access to everything and control what’s happening on each project.”

PreviousAccess Rights, Teams & User ManagementNextAB Tasty - Feature Experimentation & Rollouts Demo - How to use it

Last updated 3 days ago

Was this helpful?

👉