Create system(s) for granting/revoking access to services based on SystemAccesses, and/or updating SystemAccesses based on access to services
#643
Labels
feature
New functionality on the page
Comments
ddabble
added a commit
that referenced
this issue
May 5, 2023
Including some changes that also change semantics in minor ways: * [CONTRIBUTING.md] Replaced the examples with the custom path converters previously removed in a5eaf62 * [profile_detail.html] The script tags in `extra_head` are now only rendered if the user has the `internal.is_internal` permission, as they're only used for code in `profile_detail_internal.html` anyway * [internal/models.py] Removed the TODO comment and created an issue for it instead (#643) * [admin_event_detail.html + admin_event_ticket_list.html] Added missing `font-size` styling, to make the titles match the ones in the other admin panel pages
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
"Services" include e.g. Google Drive, Slack, email lists, etc.
For Slack and Discord, it's possible to create apps/bots for automating this, which could communicate with API endpoints on the website server. These could e.g. automatically add people to Slack channels or give them Discord roles when updating their
SystemAccesses on the website, or vice versa - i.e. updating theirSystemAccesses based on which channels they are added to or roles they are given.The same goes for Google Drive, Calendar and email lists (through Google Workspace), for which Google has created a plethora of APIs, and also the possibility of running code on their servers through Google Apps Script.
The text was updated successfully, but these errors were encountered: