Is it possible to add view-only users with no cost?

One approach is to create a link which will authenticate to a userid setup for that purpose (so you would need to pay for 1 userid)  and then redirect to a dashboard of reports and links.  Once you have that link developed, you would have to put it "somewhere" where these users can access.  Not sure where you want that "somewhere" to be.  I can help with that syntax once you are sure what you want.

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.

Indeed, understood. Will try this out and get back to you tomorrow! Thanks!

Another option is to use a "Portal", then you can have all the data be customized to the individual who logs into the portal.

That is if you are looking to filter out the unrelated data (i.e. One sales rep should not see the sales data from a different rep). 

Portals save you a lot of cost long term, and make your app much more secure than having the authentication in a button.

If you are worried about the IP that might exist in your code pages, those code pages can be seen by any and all users, regardless of role.

If you have IP concerns, using a single user approach has risks in that there is no accountability or user control. You have no way to revoke access, etc.

Using a portal is a more secure approach as Matthew mentioned. It is fully customizable and your own UI. If it is built securely (i.e., not storing the portal user's plain text password in Quick Base), this can be a valuable tool. Granted, this is more expensive, but might be worth it for you.

You want to avoid exposing credentials whenever possible.