It would be great to able to create sub tables that can be hidden (remove clutter and distraction) and only accessible via the main table which is displayed.
Interesting. Can you share a use case? There may be ways to do this with the current setup.
I know a lot of people who keep a separate table with their API keys from 3rd party programs.
1 Like
I agree there are some apps I do not wan’t accessible to all team members or directly. I only want it to be accessible through the main App in a relational field.
For example having A Projects App and Deliverables app:
I want the deliverables to always be related to a Project and only created through a project. Deliverables can become a sub app
1 Like
Hi @RichardHedger and @femi,
This is indeed a very valuable feature idea. We’ve actually been thinking about something similar under the concept of “hidden apps”, which has also been requested by other users.
As @1F2Ns already suspected, there is in fact an existing feature that allows you to provide global apps for things like helper values or similar use cases where the app doesn’t need to be directly visible to users. However, this works at the workspace level and is available organization-wide, meaning that all members of the org can still access it via global search and the All Workspaces tab.
If that’s not an issue, you can create a closed workspace and set the “Everyone else” access to at least can view. If users aren’t invited directly but only access it through this permission setting, the workspace won’t appear in their sidebar, but you can still link to apps within it or move them there from your original workspace via drag and drop as needed.
This approach can be really useful for certain use cases, though not all, which is why a proper “hidden apps” feature would definitely be a great enhancement.
Best regards
Leo
1 Like
Sure, this is a possibility but I think hidden apps is a no brainer to create simple but sophisticated workspaces.
1 Like