i was thinking about scenario where all parties involved in decision are employees or contractors working on some internal project for a single enterprise compa

i was thinking about scenario where all parties involved in decision are employees or contractors working on some internal project for a single enterprise company, and decision log is being used to record project decisions. in that case, enterprise company is the one paying the bill for loqbooq subscription, so enterprise would want to set the policy for accessing data / onboarding / offboarding. they'd want SSO integration for access control, and if SSO integration said "this user no longer has an account; access denied" then the enterprise would want loqbooq to deny access and not email out a copy of internal enterprise data. basically: if there's a disagreement between one or more parties involved in a project where loqbooq is being used, but only one of the parties is the customer paying loqbooq the monthly subscription, so wouldn't that paying customer want loqbooq do do the thing that is most in their interest? Enterprise might think through scenarios like: * "what if one of our contractors or employees foolishly/accidentally dumps customer PII into external loqbooq.app SaaS outside of our datacentres? how do we limit & do damage control over data breach?" * what if we believe that some of our employees are trying to start up a new business in competition with us, and might try to use our proprietary information to do so? (product roadmaps ; architecture docs ; lists of customers & suppliers ; ...) In both scenarios they may want a mechanism that gives company administrators a quick and reliable way to terminate user access to loqbooq and limit risk of further information leaks.