🆕 In the shared section of the sidebar – records can be grouped and opened in one app

Before:

New feature:

Result:







We are sure this new feature will make all of us rethink how we create use cases in Tape, making shared records more intuitive and organized.

Let’s start with an example: managing pay stubs for your team.

The challange

In the past, managing tasks like handling pay stubs came with certain challenges. Here are three common approaches we’ve seen:

  • One main app syncing with automations to each employee’s app: for teams with many employees, this setup required a significant number of automation runs.
  • Restricted access for individual records: admins had to assign permissions individually, making it time-consuming as the number of records grew.
  • Tracking shared records: with many shared records, staying organized was nearly impossible. In some cases, we’ve seen setups with over 5,000 shared records for a single user in the shared section :see_no_evil:.

The new solution

Now, admins can share records within an app environment. Here’s how it works:

  • In the shared section at the left sidebar, all records from the same app are grouped under the app name.
  • When users open the app, they enjoy the same benefits as any app: views, filters, and all to what they’re allowed to see.

Example:

  • As an admin, set up an “Private” workspace.
  • Add an app e.g. “Pay stubs” for your team.
  • In the app share menu, select “Anyone with shared content.”
  • Then share individual records (e.g. Pay stub December 2024) with the employee (e.g. Juliet) with any permission level (e.g. full access or can view etc.)
  • Juliet see the app “Pay stubs” in their shared section. Inside, they can only view their own pay stubs—fully sorted and organized using app features like tables, filters, and views.
  • Juliet don’t have app permissions, they can’t create new records, what is great for this use-case.

The result: one app for pay stubs, with employees accessing only their own data—no messy workarounds

What is different about sharing an entire app?

Managing permissions is the key difference. In a shared app with 10,000 pay stub records for 100 employees, you’d need to restrict access to 9,900 records for every employee—a process that isn’t practical. Every new record would also require manual restrictions, as permissions sync automatically from the app’s permission settings. However, in other scenarios, this behavior is precisely the advantage of Tape’s comprehensive permissions.


What about guests?

Guests were a big challenge during development, but we’ve made it work. With the “Everyone at [Your Org Name] and guests” setting, guests can currently benefit from this feature while still enjoying a seamless experience.


Why This Matters

Creating this feature took significant effort presenting app functionality for shared records. But we truly believe it’s worth it.
This update simplifies shared sections, making them more powerful and user-friendly. We’ve already restructured a few of our own apps, and the shared section has never felt better.
We hope it makes a difference for you too.

10 Likes

@Leo This is super awesome, thank you guys for all your hard work on this. It’s really a revolutionary feature that will have a ton of applications for many different types of systems.

If I can ask a devil’s advocate question… I see that the API documentation has been updated to create an endpoint to adjust user permissions for a given record (or records). I’m just curious if you guys have a timeline for an automation action to share an individual record in a more user friendly UI method? I assume that the automations tool will have a built in action for this at some point?

Thanks again!

2 Likes

wow, this is game changing for so many use cases.
Thanks again to the Tape Team for continuously improving and rapidly releasing such exciting new features.

I’d like to share an example for a sales portal use case that I see benefiting from this release, then ask a few clarification questions here…

Lets say there is a multi-tiered sales org that wants to limit access to deal visibility per salesman within their Deals app.

At level one there is the main, internal, Tape account users who have access to all the deals in the entire app.

For level two, each deal has a sales team tagged, and using this feature we can give access to the Team Leader to see only the deals that have been sold by salesmen on their team. Being able to see these deals grouped together as a table and saved views/filters will be much better than individual records!

Finally level three is the individual salesman that should only have access to see the deals they sold directly.

My understanding is that this will all work in a nicely organized way thanks to this new feature. Each user level at this org can see and interact with only the deal records they are invited to. Previously we would have to create many duplicated apps or external portals to make this type of limited visibility possible.

Now (I think I know this answer, but want to confirm) - will the org owner end up paying for every single person who is ultimately given shared access?

In this example, the Sales Org might have 20 team members who are really the ones using Tape for data management.
Then there might be 50 different external sales teams involved. Each of those have a Team Leader that will be given access - but not really interacting with Tape Data other than viewing the table of current deals.
Finally, each external sales team may have 3-10 reps of their own out selling. These reps also receive access to their own deals, but really just to view status updates and see if any issues get flagged post sale. (They are monitoring to make sure their final commission for the sale comes through when it finally qualifies)

So, using max values from these examples, we now see up to 20(internal)+50(external sales team leaders)+(10 external salesman*all 50 teams) = 570 possible users

We know that the Premium Plan allows to invite up to 4 guests for free, for each billed member.
So in this example, 20*4 = 80 guests allowed.
Do we have to add enough additional paid seats to get all these 500+ external sales reps ability to see their shared deals as guests?

Also, I haven’t been able to check yet, but can giving/removing access to these guests be done in bulk within the user interface?