In most oAuth applications i've used thus far there has been the ability to authorize an request, and by doing that initializing a connection returning the client id etc to the requestee. Why i need this? I need this for companies on the platform i work on can get their tasks imported into Clickup, and thus creating a central area for them to handle their tasks. The setup is like this, that there are companies, and each company can have multiple employees, which all have their own users. So we would need oAuth to connect with an App on clickup, and have those information saved on the company for us to synchronize their tasks etc to clickup from the platform. For many companies, bigger ones - the issues is minor, since they would prob. have an IT department which can handle the signup and app creation. Tho for minor / smaller companies, with less hands available to them this might not be feasible, thus i request a feature to be added to handle this. What do i sugest? I sugest that an url endpoint is created, in which the platform can send a user to, which will ask the user to firstly login or create an account through a guided wizard. And secondly it will let the user know what changes are trying to be made i.e. creating a new application, the user can then authorize or reject. If they authorize an app is created and information needed to communicate with Clickup are returned through an return uri in which the platform can handle and save the data on the company. After that the platform can syncronize with Clickup through the application. If more security is wanted, a permission setup can be set up around the app access, so when creating the app initially the platform has to ask for specific permissions to be used, depending on what the applications needs is. So the user is given information on what the application is given allowance on.
