You could share the other table’s view with them as another shared view, and give them 2 separate links — one for each view.
Alternatively, you could add them as a read-only collaborator to your base, but there are many security risks associated with that — all collaborators (including read-only collaborators) can invite other collaborators, can export all the records of your database to a CSV file, can duplicate your entire base, can see all of your API keys within blocks, and can view all of your data in all tables. In essence, they have full access to your entire system.
Otherwise, Stacker is a great way to get the best of both worlds, without any of the security risks.
You could share the other table’s view with them as another shared view, and give them 2 separate links — one for each view.
Alternatively, you could add them as a read-only collaborator to your base, but there are many security risks associated with that — all collaborators (including read-only collaborators) can invite other collaborators, can export all the records of your database to a CSV file, can duplicate your entire base, can see all of your API keys within blocks, and can view all of your data in all tables. In essence, they have full access to your entire system.
Otherwise, Stacker is a great way to get the best of both worlds, without any of the security risks.
Thank for the reply. That does solve the problem for this particular person. Appreciate the time.
Thank for the reply. That does solve the problem for this particular person. Appreciate the time.
Glad I could help!
If you don’t mind, could you please mark my comment above as the solution to your question? This will help other people who have a similar question in the future.