Personal and Public Views
Common Use Cases
- Team layouts: a public view everyone uses to work the list
- Personal focus: a private view filtered to your own items
- Experimentation: testing a layout privately before sharing it
- Role-based views: public views tailored to different audiences
- Default view: the public view that opens first for everyone
- Quiet preferences: a personal sort that does not affect others
Benefits
- Clear audience: public for the team, personal for you
- Protects the shared list: personal views cannot disrupt others
- Owner control: public views are governed by site owners
- Flexibility: users get their own arrangements when needed
- Safe testing: try a layout privately first
- Many at once: a list can hold numerous views of each kind
How It Works
- Create a view: choose Public or Personal when saving
- Public is shared: everyone with access can use it
- Personal is private: only the creator sees a personal view
- Permission to publish: creating public views requires the right permission
- Default view: one public view is set as the default
- Edit and manage: views are managed from the view menu and settings
Limits and Nuances
- Permission gate: publishing public views needs design or manage rights
- Personal views are yours alone: they cannot be shared as is
- Default is public: the default view is always a public one
- Clutter risk: too many public views confuse users
- Ownership: public views are best curated by site owners
- Not security: views organize display, they do not restrict access
Common Questions About Personal and Public Views
What is the difference between a personal and a public view?
A public view is shared with everyone who can access the list or library, so it is the place for layouts the whole team uses. A personal view is private to the person who created it, visible to no one else. The choice comes down to audience: shared layouts should be public, while individual arrangements belong in a personal view.
Who can create a public view?
Creating or editing public views requires the right permission level, typically the ability to manage lists, which usually means site owners or members with design rights. Most users can always create personal views for themselves. This split keeps the shared list tidy, since not everyone can change the layouts that the whole team depends on.
Can other people see my personal view?
No. A personal view is visible only to you. Others cannot open it, edit it, or break it, which makes personal views a safe place for private filters and sorts. If you want others to use a layout you built, you would recreate it as a public view, assuming you have permission to publish public views.
Which view opens first when someone visits the list?
The list has a default view, and that default is always a public view. It is the layout everyone sees when they first open the list, so it is worth setting the default to the most broadly useful arrangement. Personal views never act as the default for the whole list, since they belong to a single person.
Can I test a layout before sharing it?
Yes, and a personal view is the ideal way to do it. Build the columns, filters, and sorting you have in mind as a personal view, confirm it works the way you want, and then recreate it as a public view if you have permission. This keeps experiments out of everyone else view while you refine them.
How should I decide between public and personal views?
Let the audience decide. Greg Zelfond, the consultant behind LookBook 365, keeps a small set of well-named public views that site owners curate for the team, and encourages individuals to use personal views for their own preferences. That balance gives everyone a clean shared experience while still allowing personal flexibility on top of it.