Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

PlaySQL: How to implement limited access to tables from other spaces?

We are currently evaluating the usage of Play SQL Spreadsheets for Confluence. During our test phase we ran into some unexpected behaviour, which we would like to understand better.

Our setup of Play SQL Spreadsheets has one postgresql database and one postgresql user for each confluence space we want to use the plugin with. We plan to use the plugin for data, for which the storage in a database would be preferable, but we need to make sure it is not accessible for everyone who has access to the confluence instance in general.

A very specific, but important use case is the collection of data within one confluence space A and the reporting of an aggregated version of the data in confluence space B. As outlined above, space A has a database user A and own postgresql database A, whereas space B has also a database user B and database B.

Our plan was to aggregate the data as required in space A and then make those tables with only aggregated data available for user B on our postgresql instance.

This works to a certain extent, so that confluence users which can access space A and B see Play SQL graphs and tables based on the described database tables in space B. Confluence users, however, which are only allowed to access space B, cannot see Play SQL graphs and tables based on data stored in space A.

Is this behaviour desired / enforced by Play SQL Spreadsheets? And what would be a potential technical solution to enable us using the plugin in this way?

Any insight would be very welcome. Thank you in advance.

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

New cloud apps roundup - June 2021

Since our last roundup in April, Atlassian's Marketplace Partners have added over 100 new cloud apps to the Atlassian Marketplace to help your teams work more efficiently. Let’s take a quick look a...

368 views 5 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you