Skip to main content

Modeling Authorization for Slack with Auth0 FGA

note
Auth0 Fine Grained Authorization (FGA) is the early-stage product we are building at Auth0 to solve fine-grained authorization at scale. Sign up for the Developer Community Preview to try it out, and join our Discord community if you are interested in learning more about our plans.

Please note that at this point in time, it is not considered production-ready and does not come with any SLAs; availability and uptime are not guaranteed. Limitations of Auth0 FGA during the Developer Community Preview can be found here.

This tutorial explains how to model permissions for a communication platform like Slack using Auth0 FGA.

What you will learn
  • How to indicate relationships between a group of users and an object.
    Used here to indicate that all members of a slack workspace can write in a certain channel.
    See Modeling User Groups for more.
  • How to Model concentric relationship to have a certain relation on an object imply another relation on the same object.
    Used here to indicate that legacy admins have all the permissions of the more granular channels admin.
    See Modeling Concentric Relationships for more.
  • How to use the union operator condition to indicate that a user might have a certain relation with an object if they match any of the criteria indicated.

Slack

Explore the Slack sample on the Auth0 FGA Playground

Before You Start

In order to understand this guide correctly you must be familiar with some Auth0 Fine Grained Authorization (FGA) concepts and know how to develop the things that we will list below.

Auth0 FGA Concepts

It would be helpful to have an understanding of some concepts of Auth0 FGA before you start.

Modeling Basics

You need to know how to create an authorization model and create a relationship tuple to grant a user access to an object. Learn more →

Modeling Concentric Relationships

You need to know how to update the authorization model to allow having nested relations such as all writers are readers. Learn more →

Concepts & Configuration Language

What You Will You Be Modeling

Slack is a messaging app for businesses that connects people to the information they need. By bringing people together to work as one unified team, Slack transforms the way organizations communicate. (Source: What is Slack?)

In this tutorial, you will build a subset of the Slack permission model (detailed below) in Auth0 Fine Grained Authorization (FGA), using some scenarios to validate the model.

As reference, you can refer to Slack's publicly available docs:

Note: For brevity, this tutorial will not model all of Slack's permissions. Instead, it will focus on modeling the scenarios outlined below.

Requirements

This tutorial will focus on the following sections (this is a partial list of Slack's roles):

Workspace Roles:

  • Guest: This type of user is limited in their ability to use Slack, and is only permitted to see one or multiple delegated channels.
  • Member: This is the base type of user that does not have any particular administrative abilities, but has basic access to the organization's Slack workspaces. When an administrative change needs to be made, these users need the support of admins and owners to make the changes.
  • Legacy Admin: This type of user is the basic administrator of any organization, and can make a wide variety of administrative changes across Slack, such as renaming channels, archiving channels, setting up preferences and policies, inviting new users, and installing applications. Users with this role perform the majority of administrative tasks across a team.

System Roles:

  • Channels Admin: This type of user has the permission to archive channels, rename channels, create private channels, and convert public channels into private channels.

Channel Settings:

  • Visibility:
    • Public: Visible to all members and open to join
    • Private: Visible to admins and invited members
  • Posting Permissions:
    • Open: Anyone can post
    • Limited: Only allowed members can post

Defined Scenarios

Use the following scenarios to be able to validate whether the model of the requirements is correct.

There will be the following users:

  • Amy
  • Bob
  • Catherine
  • David
  • Emily

These users will interact in the following scenarios:

  • You will assume there is a Slack workspace called Sandcastle
  • Amy is a legacy admin of the Sandcastle workspace
  • Bob is a member of the Sandcastle workspace with a channels admin role (Read more about system roles at Slack here)
  • Catherine and Emily are normal members of the Sandcastle workspace, they can view all public channels, as well as channels they have been invited to
  • David is a guest user with only view and write access to #proj-marketing-campaign, one of the public channels in the Sandcastle workspace
  • Bob and Emily are in a private channel #marketing-internal in the Sandcastle workspace which only they can view and post to
  • All members of the Sandcastle workspace can view the general channel, but only Amy and Emily can post to it

Image showing requirements

caution

In production, it is highly recommended to use unique, immutable identifiers. Names are used in this article to make it easier to read and follow.

Modeling Workspaces & Channels

The goal by the end of this post is to ask Auth0 Fine Grained Authorization (FGA): Does person X have permission to perform action Y on channel Z? In response, you want to either get a confirmation that person X can indeed do that, or a rejection that they cannot. E.g. does David have access to view #general?

The Auth0 Fine Grained Authorization (FGA) is based on Zanzibar, a Relation Based Access Control system. This means it relies on objects and user relations to perform authorization checks.

Setting aside the permissions, you will start with the roles and learn how to express the requirements in terms of relations you can feed into Auth0 FGA.

The requirements stated:

  • Amy is a legacy admin of the Sandcastle workspace
  • Bob is a channels admin of the Sandcastle workspace
  • Catherine and Emily are a normal members of the Sandcastle workspace
  • David is a guest user

Here is how you would express than in Auth0 FGA'sauthorization model: You have a type called "workspace", and users can be related to it as a legacy_admin, channels_admin, member and guest

type workspace
relations
define legacy_admin as self
define channels_admin as self
define member as self
define guest as self
info

Objects of type workspace have users related to them as:

  • Legacy Admin (legacy_admin)
  • Channels Admin (channels_admin)
  • Member (member)
  • Guest (guest)

self (or this in the API Syntax) is the direct relationship keyword and indicates that a user can have a direct relationship with an object of the type the relation specifies.

01. Individual permissions

To keep things simple and focus on Auth0 FGA rather than Slack complexity, we will model only four roles (legacy_admin, channels_admin, member, guest).

At the end of this section we want to have the following permissions represented

UserRelationObject
amylegacy_adminworkspace:sandcastle
bobchannels_adminworkspace:sandcastle
catherinememberworkspace:sandcastle
davidguestworkspace:sandcastle
emilymemberworkspace:sandcastle

To represent permissions in Auth0 FGA we use relations. For workspace permissions we need to create the following authorization model:

type workspace
relations
define legacy_admin as self
define channels_admin as self
define member as self
define guest as self

The Auth0 Fine Grained Authorization (FGA) service determines if a user has access to an object by checking if the user has a relation to that object. Let us examine one of those relations in detail:

type workspace
relations
define member as self
info

The snippet above indicates that objects of type workspace have users related to them as "member" if those users belong to the userset of all users related to the workspace as "member".

This means that a user can be directly related as a member to an object of type "workspace"

If we want to say amy is a legacy_admin of workspace:sandcastle we create this relationship tuple

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

await fgaClient.write({
writes: {
tuple_keys: [
// Amy is a Legacy Admin in the Sandcastle workspace
{ user: 'amy', relation: 'legacy_admin', object: 'workspace:sandcastle'}
]
}
});

We can now ask Auth0 FGA "is amy a legacy_admin of workspace:sandcastle?"

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

// Run a check
const { allowed } = await fgaClient.check({
tuple_key: {
user: 'amy',
relation: 'legacy_admin',
object: 'workspace:sandcastle',
},});

// allowed = true

We can also say that catherine is a member of workspace:sandcastle:

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

await fgaClient.write({
writes: {
tuple_keys: [
// Catherine is a Member in the Sandcastle workspace
{ user: 'catherine', relation: 'member', object: 'workspace:sandcastle'}
]
}
});

And verify by asking Auth0 FGA

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

// Run a check
const { allowed } = await fgaClient.check({
tuple_key: {
user: 'catherine',
relation: 'member',
object: 'workspace:sandcastle',
},});

// allowed = true

Catherine, on the other hand, is not a legacy_admin of workspace:sandcastle.

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

// Run a check
const { allowed } = await fgaClient.check({
tuple_key: {
user: 'catherine',
relation: 'legacy_admin',
object: 'workspace:sandcastle',
},});

// allowed = false

Repeat this process for the other relationships

[
{
// Bob is a Channels Admin in the Sandcastle workspace
"user": "bob",
"relation": "channels_admin",
"object": "workspace:sandcastle"
},
{
// David is a guest in the Sandcastle workspace
"user": "david",
"relation": "guest",
"object": "workspace:sandcastle"
},
{
// Emily is a Member in the Sandcastle workspace
"user": "emily",
"relation": "member",
"object": "workspace:sandcastle"
}
]
Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

await fgaClient.write({
writes: {
tuple_keys: [
// Bob is a Channels Admin in the Sandcastle workspace
{ user: 'bob', relation: 'channels_admin', object: 'workspace:sandcastle'},
// David is a guest in the Sandcastle workspace
{ user: 'david', relation: 'guest', object: 'workspace:sandcastle'},
// Emily is a Member in the Sandcastle workspace
{ user: 'emily', relation: 'member', object: 'workspace:sandcastle'}
]
}
});

Verification

To verify, we can issue check request to verify it is working as expected.

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

// Run a check
const { allowed } = await fgaClient.check({
tuple_key: {
user: 'amy',
relation: 'legacy_admin',
object: 'workspace:sandcastle',
},});

// allowed = true

Let's try to verify the followings:

UserObjectRelationQueryRelation?
amyworkspace:sandcastlelegacy_adminis amy related to workspace:sandcastle as legacy_admin?Yes
davidworkspace:sandcastlelegacy_adminis david related to workspace:sandcastle as legacy_admin?No
amyworkspace:sandcastleguestis amy related to workspace:sandcastle as guest?No
davidworkspace:sandcastleguestis david related to workspace:sandcastle as guest?Yes
amyworkspace:sandcastlememberis amy related to workspace:sandcastle as member?No
davidworkspace:sandcastlememberis david related to workspace:sandcastle as member?No

02. Updating the workspace authorization model with Implied Relations

Some of the queries that you ran earlier, while returning the correct response, do not match reality. One of which is:

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

// Run a check
const { allowed } = await fgaClient.check({
tuple_key: {
user: 'amy',
relation: 'member',
object: 'workspace:sandcastle',
},});

// allowed = false

As you saw before, running this query will return amy is not a member of workspace:sandcastle, which is correct based on the data you have given Auth0 Fine Grained Authorization (FGA) so far. But in reality, Amy, who is a legacy_admin already has an implied channels_admin and member relations. In fact anyone (other than a guest) is a member of the workspace.

To change this behavior, we will update our system with a concentric relationship model.

With the following updated authorization model, you are informing Auth0 Fine Grained Authorization (FGA) that any user who is related to a workspace as legacy_admin, is also related as a channels_admin and a member .

type workspace
relations
define legacy_admin as self
define channels_admin as self or legacy_admin
define member as self or channels_admin or legacy_admin
define guest as self

We can then verify amy is a member of workspace:sandcastle.

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

// Run a check
const { allowed } = await fgaClient.check({
tuple_key: {
user: 'amy',
relation: 'member',
object: 'workspace:sandcastle',
},});

// allowed = true

We can check for other users and relationships.

UserObjectRelationQueryRelation?
amyworkspace:sandcastlelegacy_adminis amy related to workspace:sandcastle as legacy_admin?Yes
davidworkspace:sandcastlelegacy_adminis david related to workspace:sandcastle as legacy_admin?No
amyworkspace:sandcastleguestis amy related to workspace:sandcastle as guest?No
davidworkspace:sandcastleguestis david related to workspace:sandcastle as guest?Yes
amyworkspace:sandcastlememberis amy related to workspace:sandcastle as member?Yes
davidworkspace:sandcastlememberis david related to workspace:sandcastle as member?No

03. Updating the Authorization Model to include Channels

So far, you have modeled the users' relations to the workspace itself. In this task you will expand the model to include the relations concerning the channels.

By the end of it, you will run some queries to check whether a user can view or write to a certain channel. Queries such as:

  • is david related to channel:general as viewer? (expected answer: No relation, as David is a guest user with only a relation to #proj-marketing-campaign)
  • is david related to channel:proj_marketing_campaign as viewer? (expected answer: There is a relation, as there is a relation between David and #proj-marketing-campaign as a writer)
  • is bob related to channel:general as viewer? (expected answer: There is a relation, as Bob is a member of the Sandcastle workspace, and all members of the workspace have a viewer relation to #general)

The requirements are:

  • Amy, Bob, Catherine and Emily, are normal members of the Sandcastle workspace, they can view all public channels, in this case: #general and #proj-marketing-campaign
  • David, a guest user, has only view and write access to the #proj-marketing-campaign channel
  • Bob and Emily are the only ones with either view or write access to the #marketing-internal channel
  • Amy and Emily are the only ones with write access to the #general channel

The possible relations to channels are:

  • Workspace includes the channel, consider the relation that of a parent workspace
  • A user can be a viewer and/or writer on a channel

The authorization model already has a section describing the workspace, what remains is describing the channel. That can be done by adding the following section to the configuration above:

type channel
relations
define parent_workspace as self
define writer as self
define viewer as self
info

The configuration snippet above describes a channel that can have the following relations:

  • workspaces related to it as parent_workspace
  • users related to it as writer
  • users related to it as viewer

Implied relation

There is an implied relation that anyone who can write to a channel can also read from it, so the authorization model can be modified to be:

type channel
relations
define parent_workspace as self
define writer as self
define viewer as self or writer
info

Note that the channel type definition has been updated to indicate that viewer is the union of:

  • the set of users with a direct viewer relation to this object
  • the set of users with writer relations to this object

As a result, the authorization model is:

type workspace
relations
define legacy_admin as self
define channels_admin as self or legacy_admin
define member as self or channels_admin or legacy_admin
define guest as self
type channel
relations
define parent_workspace as self
define writer as self
define viewer as self or writer

Updating relationship tuples

What remains is to add the relationship tuples to indicate the relation between the users, workspace and the channels.

The Sandcastle workspace is a parent workspace of the #general, #marketing-internal and #proj-marketing-campaign channels.

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

await fgaClient.write({
writes: {
tuple_keys: [
{ user: 'workspace:sandcastle', relation: 'parent_workspace', object: 'channel:general'},
{ user: 'workspace:sandcastle', relation: 'parent_workspace', object: 'channel:marketing_internal'},
{ user: 'workspace:sandcastle', relation: 'parent_workspace', object: 'channel:proj_marketing_campaign'}
]
}
});
#general channel

The #general channel is a public channel visible to all the members of the workspace. In Auth0 FGA, you represent this relation in the form of the following relationship tuple:

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

await fgaClient.write({
writes: {
tuple_keys: [
// The set of users related to `workspace:sandcastle` as member are also related to `channel:general` as `viewer`
{ user: 'workspace:sandcastle#member', relation: 'viewer', object: 'channel:general'}
]
}
});
info

This indicates The set of users related to workspace:sandcastle as member are also related to channel:general as viewer

And to indicate that Amy and Emily can write to it:

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

await fgaClient.write({
writes: {
tuple_keys: [
// Due to the configuration update you added earlier, writer relation is enough to imply a viewer relation
{ user: 'amy', relation: 'writer', object: 'channel:general'},
{ user: 'emily', relation: 'writer', object: 'channel:general'}
]
}
});
#marketing-internal channel

The #marketing-internal is visible to only Bob and Emily. They can view and write in it.

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

await fgaClient.write({
writes: {
tuple_keys: [
{ user: 'bob', relation: 'writer', object: 'channel:marketing_internal'},
{ user: 'emily', relation: 'writer', object: 'channel:marketing_internal'}
]
}
});
#proj-marketing-campaign channel

The #proj-marketing-campaign is public to all members of the Sandcastle workspace. They can view and write in it.

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

await fgaClient.write({
writes: {
tuple_keys: [
{ user: 'workspace:sandcastle#member', relation: 'writer', object: 'channel:proj_marketing_campaign'}
]
}
});

David is a guest user who can also view and write to #proj-marketing-campaign

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

await fgaClient.write({
writes: {
tuple_keys: [
{ user: 'david', relation: 'writer', object: 'channel:proj_marketing_campaign'}
]
}
});

Verification

Now that you have added the necessary relationship tuples, you will check to make sure that your configuration is valid.

First, we want to ensure david is not related to channel:general as viewer.

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

// Run a check
const { allowed } = await fgaClient.check({
tuple_key: {
user: 'david',
relation: 'viewer',
object: 'channel:general',
},});

// allowed = false

David should be related to channel:proj_marketing_campaign as viewer.

Initialize the SDK
// FGA_ENVIRONMENT can be "us" (default if not set) for Developer Community Preview or "playground" for the Playground API
// import the SDK
const { Auth0FgaApi } = require('@auth0/fga');

// Initialize the SDK
const fgaClient = new Auth0FgaApi({
environment: process.env.FGA_ENVIRONMENT,
storeId: process.env.FGA_STORE_ID,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
});

// Run a check
const { allowed } = await fgaClient.check({
tuple_key: {
user: 'david',
relation: 'viewer',
object: 'channel:proj_marketing_campaign',
},});

// allowed = true

Repeat this for the following relations

UserObjectRelationQueryRelation?
amyworkspace:sandcastlelegacy_adminis amy related to workspace:sandcastle as legacy_admin?Yes
amyworkspace:sandcastlememberis amy related to workspace:sandcastle as member?Yes
amyworkspace:sandcastlechannels_adminis amy related to workspace:sandcastle as channels_admin?Yes
amychannel:generalwriteris amy related to channel:general as writer?Yes
amychannel:generalvieweris amy related to channel:general as viewer?Yes
amychannel:marketing_internalwriteris amy related to channel:marketing_internal as writer?No
amychannel:marketing_internalvieweris amy related to channel:marketing_internal as viewer?No
emilychannel:marketing_internalwriteris emily related to channel:marketing_internal as writer?Yes
emilychannel:marketing_internalvieweris emily related to channel:marketing_internal as viewer?Yes
davidworkspace:sandcastleguestis david related to workspace:sandcastle as guest?Yes
davidworkspace:sandcastlememberis david related to workspace:sandcastle as member?No
davidchannel:generalvieweris david related to channel:general as viewer?No
davidchannel:marketing_internalvieweris david related to channel:marketing_internal as viewer?No
davidchannel:proj_marketing_campaignvieweris david related to channel:proj_marketing_campaign as viewer?Yes

Summary

In this tutorial, you:

  • were introduced to fine grain authentication and Auth0 FGA.
  • learned how to build and test an Auth0 Fine Grained Authorization (FGA) authorization model for a communication platforms like Slack.

Upcoming tutorials will dive deeper into Auth0 Fine Grained Authorization (FGA), introducing concepts that will improve on the model you built today, and tackling different permission systems, with other relations and requirements that need to be met.

Slack

Explore the Slack sample on the Auth0 FGA Playground

If you are interested in learning more about Authorization and Role Management at Slack, check out the Auth0 Fine Grained Authorization (FGA) team's chat with the Slack engineering team.

Exercises for You

  • Try adding more relationship tuples to represent other users and channels being added. Then run queries to make sure that the authorization model remains valid.
  • Update the configuration to model more Slack permissions (workspace owners, Slack orgs), then add the relationship tuples necessary and run some queries to validate your configuration.

Have Feedback?

Join us on the Discord community if you have any questions or suggestions.