Page tree
Skip to end of metadata
Go to start of metadata

Important

By default, you can query tables from another schema using the schema name. If your space key is 'DS', you can use SPACE_DS.TABLE_NAME. See the last section of this page.

Spreadsheets and Queries

Spreadsheets and queries are local to a Space, so they inherit the same permissions.

Space PermissionsSpreadsheet permission
ViewView, Sort
Create pageCan add and edit spreadsheets
Remove pageCan remove spreadsheets

Space Admin (if configured in Play SQL Settings)

or Confluence Admin

Can edit the datasource

Cross-space macros

When you insert a macro, the "Recently Viewed Spreadsheets" shows spreadsheets from other spaces:

Don't forget that the permissions of the original space apply to the data. Therefore if the audience of the new space doesn't match, you'll have to tune the permissions. See next paragraph.

Space-level permissions

Since  PLAYSQL-135 - Permissions to restrict editing of spreadsheets Closed , it is possible to change the permissions of spreadsheets at a space level.

  • By default in Play SQL, there are permissions for:
    • View: Viewing all data, filtering and sorting,
    • Edit: Edit rows, add rows,
    • Structure: Edit columns, change types,
    • Admin: Change the datasource properties.
  • The space permissions apply: Only users who can view the space can view spreadsheets, etc.
  • It is possible to enlarge the audience: "Accepted Groups" are groups which are accepted in addition to the space users. If the "Inherit from space" checkbox is unticked, only the accepted groups will be allowed.
  • It is possible to restrict the audience: For example administrators could decide that only Board Members can see the data. The group "Board Members" will be added to Required Groups.
  • It is possible to specify a database password for each level.

Database schema visibility

By default, Play SQL creates one schema per space:

  • You can always access a table from another schema using SPACE_[space key].TABLE_NAME.
  • If you want to isolate schemas, you'll need to create a separate Postgres user for each schema and configure a separate connection for each.

 

  • No labels