<aside> 💡 Provide detailed descriptions of the system's major components, modules, or services. Explain their responsibilities, interactions, and interfaces. Include diagrams, flowcharts, or UML diagrams to illustrate the system's structure and component interactions. Present the architectural patterns, such as client-server, microservices, or layered architecture, employed in the system design.
</aside>
Save time in access management to these Web2 tools (Notion, Linear, Trello, Figma, Asana etc) for Web3 organisations that have large number of members and contributors — this includes managing access levels of view/read only, edit, and removal(banning) when they are no longer a member of the team or organisation → This is obviously the easy part, which involves revoking their Single Sign-On credentials (for Web2 based organisations) or searching and removing them for web3 organisations.