Best way: Share or Publish?

Sylvia Kay

I have a product team that manages an issue log for a long-term program with frequent change.

• Ability to enter new issues
• Ability to create reports
• Ability to create filters

There is a leader team for the actual user group that needs to translate the technical issue int a user group-friendly language.

• Ability to edit certain columns
• Ability to create reports
• Ability to create filters

There is user group that relies on an up-to date view of which issues are open or closed.

• Ability to view the same certain columns
• Ability to open / close groupings (issue category)

Providing everyone with Admin rights creates a security concern for our Master Issue Log.

Editors cannot create their own reports

Viewers cannot open/close groupings

What are other options for me to manage this?

Ray Lindstrom

Julie Fortney

Your first two user types will need to be Admins on the sheet in order to create reports. If you have security concerns, could you consider breaking the master log into separate regions or types? For instance, if the master log currently includes data for Regions A, B, and C, and the leaders in Region A shouldn't be able to see data for Regions B & C, create three separate logs. This could be a challenge if you're referencing the master log in formulas, but your high-level reports can pull from all three sheets.

Your users could just be viewers on the published reports.

Ray Lindstrom

You don't need to be an Admin on a Sheet to create a Report based off it. Viewers of a Sheet can create Reports based off of it. You do have to be licensed though.