4 ms·
Seems like an actual use case for a spreadsheet. Is there anything you need from this tool that a trivial spreadsheet won’t support?
by cimmanom 7y ago
Seems like an actual use case for a spreadsheet. Is there anything you need from this tool that a trivial spreadsheet won’t support?
- proszkinasenne2 7y agoComprehensive and up to date overview on the access information. Github is in charge of a tech team lead, Slack is someone else. Once an employee leaves, I want to make sure access is limited accordingly. Sending a bunch of emails and coordinating, then double-checking is the worst nightmare. If the # of services you use is 5 it's all good. If you use >5 you have to check each individually every employee sign-off. We once had an ex-employee receiving Github updates two years after he left us.
- cimmanom 7y agoWhat is it that you’re looking for your tool to do about this?
- proszkinasenne2 7y ago"Comprehensive and up to date overview on the access information" by pulling data from the services I use and (optionally) managing the permissions for me. Rippling [1] calls it "provisioning/de-provisioning" and that's exactly what I am looking for (maybe with periodical checks to make sure we remove contractors permissions once their job is done) with the exception that I don't want to set up a new HR system just to get this feature. [1] - https://www.rippling.com/provisioning-de-provisioning/ https://www.rippling.com/provisioning-de-provisioning/