Announcing Role-Based Access Control (RBAC)

We're excited to announce that we've launched Role-Based Access Control (RBAC) for both users and API keys. This has been one of the most frequently requested features since we began building Vertex, and today it is live for all early access beta users.

Security and access control are some of the most important considerations when collaborating with a team of users, so we want to make sure every team can give their team members the right level of access.

Most excitingly, you can differentiate between users that have write access to just the data (editors) and users who can actually change the database schema (architects). This is a big deal, since changing a database schema often has consequences to the systems that use it. Our goal is to allow you to safely share access with non-technical users on your team and let them create their own views without worrying about them accidentally changing something that could affect the way that your application functions.

The full list of supported roles is:

Viewer

• Read only access

Editor

• Everything that a Viewer can do, plus:
• Create, edit, and delete rows and cells
• Create, edit, delete views and change sorting, filter, and hiding / showing of columns
• Can not modify the actual database schema (tables and column structure or datatypes)

Architect

• Everything that an Editor can do, plus:
• Create, edit, and delete database schemas (tables and columns)
• Create, edit, and delete databases

Admin

• Everything that an Architect can do, plus:
• Invite and remove users
• Change user roles
• Create and remove API keys

Owner

• Everything that an Admin can do, plus:
• Manage account (eg billing, plan)

‍

And we're still dreaming: in the future, we hope to make it possible for you to define even more granular permissions, including defining your own user roles and setting per-database, table, view, and row-level permissions. If you're interested in even more granularity, we'd love to hear your thoughts.