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.
This is not something I have plans for in the near future because of the complexity and the wide other range of feature requests it would attract due to bigger clients (permissions, roles, audit logs, SSO, SLA, etc...). But I might do it at some point if I want to target bigger clients.
Organizations - I would like to group some checks into organizations with their own settings (billing / members / notifications / webhook / API / etc..)
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.
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
It would be great to be able to configure a github organization in the settings and share the same checks between all members of the same organization.
The lack of this makes updown.io a complete non-starter vs. its competitors for us. It's unfortunate as I like the clean interface and clear settings otherwise.
This is not something I have plans for in the near future because of the complexity and the wide other range of feature requests it would attract due to bigger clients (permissions, roles, audit logs, SSO, SLA, etc...). But I might do it at some point if I want to target bigger clients.
This is my top feature i'd love you to add in some form. Maybe if it was part of the slack integration so anyone on the slack channel could do a couple of limited commands like add new alert. So slack is handling the authorization etc?
I suppose in theory with the API's available someone else could build this. If anyone does be sure to note it here!
Reading the comments, it appears that the approach of "everyone is an admin" is the most requested. It is more about reliability and securing the account than about delegating some checks here and there.
20 Comments
It would really help freelancers recommend updown to their clients (without team accounts, it's more complicated).
Too much ability for certain people to abuse
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.
This is not something I have plans for in the near future because of the complexity and the wide other range of feature requests it would attract due to bigger clients (permissions, roles, audit logs, SSO, SLA, etc...). But I might do it at some point if I want to target bigger clients.
Organizations - I would like to group some checks into organizations with their own settings (billing / members / notifications / webhook / API / etc..)
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.
Also a big one for us!
At least an additional "readonly" user for the status pages would be good.
@Frank if you publish your status page you can then share the link for read-only access to unauthenticated people.
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
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.
Agree with this, shared logins is a no-no for us from an InfoSec point of view
It would be great to be able to configure a github organization in the settings and share the same checks between all members of the same organization.
Super needed!
Same here : I have to add coworkers that need to add URLs in updown.io ; I changed to some common email but that's not a good way to go.
This would be very useful for us.
The lack of this makes updown.io a complete non-starter vs. its competitors for us. It's unfortunate as I like the clean interface and clear settings otherwise.
Totally understandable, thanks for your feedback.
This is not something I have plans for in the near future because of the complexity and the wide other range of feature requests it would attract due to bigger clients (permissions, roles, audit logs, SSO, SLA, etc...). But I might do it at some point if I want to target bigger clients.
This is my top feature i'd love you to add in some form. Maybe if it was part of the slack integration so anyone on the slack channel could do a couple of limited commands like add new alert. So slack is handling the authorization etc?
I suppose in theory with the API's available someone else could build this. If anyone does be sure to note it here!
Reading the comments, it appears that the approach of "everyone is an admin" is the most requested. It is more about reliability and securing the account than about delegating some checks here and there.
Sign in to comment