User access transition guide
Introducing Role-Based Access Control (RBAC) on MK.IO
We’re excited to announce the introduction of Role-Based Access Control (RBAC) to MK.IO. This powerful new feature will allow you to better manage access and permissions within your account by defining roles with specific authorizations.
Here's what you need to know:
What’s changing?
- Current Setup (v1): You’re currently using a simple authorization model (v1) to manage access.
- New setup (v2): We’re upgrading to an enhanced RBAC system (v2), providing more flexibility and control.
In v2, a new “Everyone” team gives all users access to all of your organization's projects, but you can adjust this to define more granular permissions as needed.
Timeline & actions
- Step 1: From now, and during the transition phase, both v1 and v2 will be active, giving you time to reconfigure your access settings at your own pace. Please note, the most restrictive rule between v1 and v2 will be applied.
- Step 2: Starting from November 19th (TBD), we will deactivate v1. If no changes are made by this date, all users in an organization will have access to all projects.
We recommend reviewing your Administrators to ensure you are satisfied with the set of people who have full control over your projects. If you had previously segmented access to your projects, we strongly encourage you to review your permissions and adjust them using the new RBAC model. For detailed guidance, please refer to our documentation.
Feel free to reach out to our support team if you have any questions or need assistance during this process.
Updated 11 months ago