Suppose an editorial team shares a Base of upcoming posts. One editor wants to see only drafts assigned to them, while another teammate needs the full publishing queue.
If someone changes the filters, sort order, or hidden columns in a saved view, will everyone who opens that view see the change? Is there a way to keep a personal view alongside the team's shared view?
Yes. In Busabase, the filters, sort order, and visible columns of a saved view belong to that view. If someone updates the shared view immediately, teammates who open it will see the new settings. If the change is submitted for review, the shared view changes after that request is merged.
For now, you can create a separately named view for each editor, filter it to their assigned drafts, and leave the team's publishing view unchanged. These are still views of the same Base: they are not private to one person and do not restrict access to records.
There is not yet a personal view visible only to its owner. Which would help more in this workflow: temporary filters that affect only your current session, or a private saved view you can return to later? We would like to understand which part causes the most friction for the team.
*Editor’s note: This English scenario was adapted by the Busabase team from an earlier community discussion.*
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in