Teams aka multiple users per account
Ian S. commented
Agree with this, shared logins is a no-no for us from an InfoSec point of view
Jonathan Putney commented
How is this not a feature yet? It's crazy that I need to share an account with my team in order to get new sites added.
This is a must for us. This product is great and we've been using it for 3 months, but our internal auditors don't like that it's a single account product. For that reason alone, management is considering switching to a worse product.
We need to satisfy:
- Use Named accounts, aka no shared accounts
- Redundancy, so that if someone leaves or is separated from the company, payment info can be updated and the account managed
@Frank if you publish your status page you can then share the link for read-only access to unauthenticated people.
Frank Tegtmeyer commented
At least an additional "readonly" user for the status pages would be good.
Derry Holt commented
Also a big one for us!
Bart Laarhoven commented
Yes please! Shared user accounts is very old-fashioned and frowned upon in security context. Please give me the ability to give my colleagues their personal account to access our company's checks.
Organizations - I would like to group some checks into organizations with their own settings (billing / members / notifications / webhook / API / etc..)
Miles Carmany commented
I would love to have a team member be able to view the status for sites I don't otherwise need a public page for. As it currently stands they would need my login to do this.
Too much ability for certain people to abuse
It would really help freelancers recommend updown to their clients (without team accounts, it's more complicated).