Learn how to create table views that are dynamically filtered based on the current user.
Within Coda, you can easily create filtered table views that show only the information you need, when you need it. Not only can you create static filters, such as “show me all tasks owned by Anna B.” But you can also create dynamic filters that filter the data differently depending on given factors. One such dynamic filter is a user-specific filter, which will show different data depending on the current viewer of the table. For instance, you can use a user-specific filter to create a “Personal Tasks” table that shows each different user only the tasks they personally own.
To learn all about creating these user-specific table views, continue reading.
Within this article, you’ll find...
Create a user-specific view
Let’s start with an example. You and your team have a table of all your tasks (named “Tasks”). The “Tasks” table allows the team to see all tasks across the team, which is useful for visibility. But you also want each team member to have a more focused, less noisy view of only their own personal tasks. You could create a separate view for each individual team member, with a static filter that only shows tasks owned by that team member - but this could result in a lot of views, especially if you have a large team. So instead, we recommend you create one user-specific view with a dynamic filter.
To create that user-specific view, just follow these steps:
Create a new connected view of your main table (the Tasks table, from our above example). We’ll call this new view “Personal Tasks”. This view can live on the same page as your main table or on a separate page. See instructions for creating views here.
Hover over the newly created view, and select Options in the upper right corner
Select Filter from the menu
-
In the right panel, click the + Add filter button, and select your People column from the options (in our example, this is the “Owner” column).
Note that People columns are required for creating user-specific views. Learn more about People columns here.
Now select the Current user from the list of options. This will create the dynamic filter, so that the view shows only rows where the contents of the people column match the current user of the doc.
That’s it! You now have a view that is filtered based off the current user. When Teammate A views the new table, they will only see tasks owned by Teammate A. When Teammate B views the table, they will only see tasks owned by Teammate B. And so on. You can add other filters, change the table display, and make other adjustments as needed.
FAQs
What is a user-specific view?
A user-specific view is a dynamic view that changes based on the current user of the doc. The view is filtered using a formula that takes into account the current user or viewer. Each user may therefore see a different set of rows in the user-specific view.
Do user-specific views work for my teammates who have view-only access to the doc?
Yes! As long as the user is logged into Coda and viewing the doc, the user-specific filter should work as expected.
Are people columns required for user-specific views?
Yes, People columns are a required piece of the puzzle for creating user-specific views. You cannot, for instance, use a simple text column with the user’s name. Coda uses this People column to compare against the current logged-in user. If the current logged-in user matches the person selected in the People column, that row will be displayed in the user-specific view.
What formula is used for user-specific views?
With Coda’s easy filter builder, you shouldn’t need to write any formulas to create a user-specific view. But if you’re a formula lover and want to write your own filter formula for any reason, you can use the User() formula.
Can user-specific views be used to securely hide private rows?
No - user-specific views are only intended for convenience and organization, and we we do not recommend using them for any privacy purposes. For instance, you should not count on a user-specific view to hide private rows that should not be exposed to certain doc viewers.