IAM Introduction

4 + 3 Key Concepts Structure

With our IAM, we define the platform to do things based on 4 key concepts. They are

  1. Groups
  2. Users
  3. Roles
  4. Permissions (Policies)

In order to make our permissions control more flexible and dynamic, we also added

to help define and breakdown more permission details.

Unit Breakdown

For permissions, we want it to be as detailed as possible so that in our products we can do a lot of flexible content control, what can be seen and what can't.

Actions

The smallest unit within our IAM architecture is actions. They are the list of actions of approve/deny. For example, when processing a ticket, we may have actions such as cancel/revise/process, they can be used as our action words and used to combine with resources to generate a certain permission rule.

Resources

In our current design, resources could mean a lot from BU naming to certain page components. They have a parent-child relationship with actions. For example, BU 188/SBK could be one of the resources and same apply to our content components such as ticket or a server cost table. Each resource object can be nested inside another resource object. ie. 188.ticket.status

Apps/Services