Define AlloyDB Permissions

Use the AlloyDB Permission Editor to define a permission for a database or table in a AlloyDB physical model.

Permissions are supported for the following objects in AlloyDB:

  • Schema
  • Database
  • Table
  • Tablespace
  • Column
  • Function
  • User Defined Type
  • Sequence
  • Materialized View
  • View

To define a AlloyDB permission

  1. In the Model Explorer, under one of the objects mentioned above, right-click Permissions and click New.

    An instance of Permission is created.

  2. Right-click the instance and click Properties.

    The AlloyDB Permission Editor opens.

  3. In the navigation grid, select the permission that you want to define and work with the following options:

    Click New New icon in property editors to create a new object on the toolbar to create a permission. Use the Enter filter text box to filter a very large list of permissions to quickly locate the one that you want to define.

    Name

    Specifies the name of the permission. Set the name of the permission in this field.

    With Grant

    Specifies whether the user can grant this permission to other users or not.

    Generate

    Generates SQL during forward engineering. Clear the check box if you do not want to generate SQL.

  4. On the AlloyDB tab, work with the following options:
    Owner

    Specifies the owner of the permission. Select a role from the drop-down list or click the New icon to open the PostgeSQL Role Editor and create one.

    Permission

    Specifies the type of privilege against the selected owner and permission.

  5. (Optional) Click the Comment tab and enter any comments that you want to associate with the object.
  6. (Optional) Click the Where Used tab to view where the object is used within the model.
  7. (Optional) Click the UDPtab to work with user-defined properties for the object.
  8. (Optional) Click the Notestab to view and edit user notes.
  9. (Optional) Click the Extended Notes tab to view or edit user notes.
  10. Click Close.

    The permission is defined and the AlloyDB Permission Editor closes.

For more information, refer to AlloyDB documentation.