OK, so what you would do is to use a field in any app to help you generate the URLEncoding unless you are some kind of whiz who likes doing that manually.
The formula would be
https://mycompany.quickbase.com/db/main ?act=API_Authenticate&username=myuserid
&password=my password
&rdr=" & urlencode("
https://mycompany.quickbase.com/db/xxxxxxx)
where xxxx is the home page of your app.
If you leave the link text blank and do not show it as a button, then the URL will be exposed for you to copy and paste "somewhere"
I really have no idea how this will work or not work with single sign on. But assuming that it does work, if you allow regular QuickBase users to click that link it will change their sign on to this generic userid, which of course has extremely limited access. That will confuse the heck out of them and cause support tickets to you like "why can't I access my usual QuickBase apps". They will have to log out and then sign on again to get back their full access. So this link is meant to be used only for the non QuickBase users.
