You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As is, the stats page is just accessible by being signed into the app and visiting {root url}/stats
As it gets more use and expands, we have to consider to whom we are giving access to that information and how they can access it. One option may be to create a special privilege for users. The downside of this is managing who we give those permissions to. Another option would be a shared "secret password" that involves something like a secret key combination. We could also just obfuscate the URL more and share that path to anyone who wish.
This is an exploratory ticket, so please share your thoughts on what is best. The best solution will depend somewhat on what ends up being on the stats page when all is said and done, so we might have different entry points at different stages.
The text was updated successfully, but these errors were encountered:
As is, the stats page is just accessible by being signed into the app and visiting {root url}/stats
As it gets more use and expands, we have to consider to whom we are giving access to that information and how they can access it. One option may be to create a special privilege for users. The downside of this is managing who we give those permissions to. Another option would be a shared "secret password" that involves something like a secret key combination. We could also just obfuscate the URL more and share that path to anyone who wish.
This is an exploratory ticket, so please share your thoughts on what is best. The best solution will depend somewhat on what ends up being on the stats page when all is said and done, so we might have different entry points at different stages.
The text was updated successfully, but these errors were encountered: