▲ | lousken 2 days ago | ||||||||||||||||||||||||||||||||||||||||
> Part of the problem is that every identity provider is different. So you'd have to provide docs for every single one of them and their particularities. no, you just provide the most used ones, once you have like top 5, that helps a lot > And customers don't necessarily read the docs, or even if they do they don't configure everything correctly. so just like with any other feature, really also you should be improving docs, if they are not clear, make them clearer it's basic sysadmin stuff, eventually 90% will understand and 10% will ask regardless of what you do, so just embrace yourself for those occasions | |||||||||||||||||||||||||||||||||||||||||
▲ | stackskipton 2 days ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||
>also you should be improving docs, if they are not clear, make them clearer I've written the docs with a tons review and feedback, this saying comes to mind: "Nothing is foolproof to a sufficiently talented fool" There are no more sysadmins at most companies, it's just desktop support and maybe Office365 admin who was desktop support but got promoted because they were elite ClickOps. Powershell/Terraform, that's for those DevOps people over there and they want nothing to do with us. | |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||
▲ | skywhopper 2 days ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||
The necessary docs are for the SSO system. So while we can build the docs, those UIs change often and without notice, and each customer may see something different, depending on their individual config or permissions. It’s literally impossible to “just provide better docs” consistently without incurring heavy expense… thus the extra cost. | |||||||||||||||||||||||||||||||||||||||||
|