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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


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

You can copy a macro from a page and paste it in another space. When you do so, macros contain a tag with the original space's name, so users run the macro as if they used the original space. As a consequence:

  • In one space, you can display data from several spaces,
  • Users however need permissions on those spaces to see your data,
  • So you can't hide the original space with the intent of showing data in another space.

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