This would be super useful as it avoids the need to create a view for every team member. Our team has some long term members but also a few changing staff.
It’d be great to have this “Me” view ready to go for existing team members and as new staff join.
+1 @Vernon_Fowler and @Adam_Dowsett that’s excatly my urgent needs thanks for this
+1 This would be SO useful for medium and large teams.
Obviously a must have for us too :slightly_smiling_face: Would be cool to also have this in forms (pre-filling inputs is already possible, but with static values, like “?fieldname=collaborator” --> “?fieldname=ME”
Just spent 10 mins trying to figure out if there was a way to do this, I think this would be a great addition
+1
Let’s call it “filter by currently logged-in collaborator” … is a must-have feature.
This is essential - I’m doing work for clients where I’m having to build multiple copies of views (as I’m sure everyone is).
It would be great if this filter could be locked, so that collaborators can only see their own records (depending on their role). This significantly expands the market for Airtable to uses like helpdesk/issue reporting, employee expense submission, and any other case where people should be able to add, edit, and view only their records.
It would be great if this filter could be locked, so that collaborators can only see their own records (depending on their role). This significantly expands the market for Airtable to uses like helpdesk/issue reporting, employee expense submission, and any other case where people should be able to add, edit, and view only their records.
Yes! This!
This would make the collaborator field really useful.
+1 for this it would be great for teams.
Mehdi
Any news on this? We’d love to see this feature as well!
Has there been any movement on this at all? I’d really like to know if its even being considered as a future capability (or if a workaround has been discovered)?
Thanks
Andy
Also see this as being a pretty core feature.
How would you handle whishlist ?
For instance,
- I have a table with products
- I have a table with whished items
So I’d like to filter on {colaborator} whished items and if possible don’t let see others whishes
(I’m looking for a small hack to avoid a custom whishlist app with AirTable as a backend)
How would you handle whishlist ?
For instance,
- I have a table with products
- I have a table with whished items
So I’d like to filter on {colaborator} whished items and if possible don’t let see others whishes
(I’m looking for a small hack to avoid a custom whishlist app with AirTable as a backend)
One way to handle a wish list:
If a dynamic filter based on logged in user (collaborator) is implemented, you could couple this with a locked view grid. That way users could see a wish list table filtered to only show records with them as (one of?) the wisher(s) - aka the logged in user.
Consider whether the collaborator field should allow multiples or be restricted to a single collaborator.
Thanks,
My idea was to be able to let collaborators to add new whish (not only a view)
The AirTable mobile app is really clean and could be reuse for that kind of use instead of building a new app
I am also creating multiple views with different filters based on a collaborator field. It’s very frustrating, as it seems like filtering by current viewer is such an obvious use of this field type!
This would be amazing as it avoids the need to create a view for every team member, who is using exactly the same view, with the only difference being that the filter is adjusted to them as collaborator, so only their items visible.
We end up with:
Tracker (John)
Tracker (Tony)
Tracker (Joan)
When it should be just one tracker with a dynamic collaborator filter.
We are continually upgrading our workflow so having to change every single view for every member every time is a bit of a blocker for us.
+1
We would also really like to see this. Having the same view for different people is a very common use-case
+1
We would also really like to see this. Having the same view for different people is a very common use-case
Welcome to the community @Mayhul_Arora :slightly_smiling_face:
Thanks for your +1 vote for this product suggestion.
Views filtered to the logged in user seem even more relevant now that the Web Clipper block has been updated with the option to choose a default value of the Clip action user for collaborator fields.
1+ this. This will help reduce the number of views in a base which I know is a main complaint with the lack of cross base linking. I’m currently running 30 views in a base and could reduce these by about 12 if I could filter based on user.
1+ this. This will help reduce the number of views in a base which I know is a main complaint with the lack of cross base linking. I’m currently running 30 views in a base and could reduce these by about 12 if I could filter based on user.
Agreed to all. +1 on feature add. I’ve built a custom ‘user dashboard’ but it has to be shared with each user manually and doesn’t allow for widescale distribution or edits.
+1. Would love users to not have to create their own views - that we then can’t keep up to date when things change.
Very much missing to create views that are relevant to the current user.
