Allow ability to associate Tags to Cards so that you can have Cards in multiple collections and packages. If it's not via Tags then simply how can I have 1 Card live in multiple places across collections and cards
This likely warrants two separate feature requests.
Ability to add tags to cards (which is likely a subset of the ability to add metadata to cards).
Ability to have cards live in multiple collections without manual assignment/loading (much more complicated request).
I'm adding my vote to the ability to add tags to cards (and subsequently the ability for end users to see and filter cards in Sidekick or base by tags).
Skyler Reeves
•
May 21, 2025
Chiming in again to say Tags > Folders with respect to knowledge management.
I’m in that camp that thinks Folders are useful for two things: (1) partitioning information and (2) access control.
Partitioning is already handled in virtue of how Bases work by default. And Access Control is handled through Bases and Share settings.
I have yet to see a company not create absolute fucking bedlam when using folders to organize knowledge—especially when Cards cannot simultaneously live in multiple directories.
The DRY principle inevitably gets violated when information is applicable in multiple contexts but duplicate cards are needed due to access control settings and/or basic user behavior.
Give users folders and a search bar and some percentage of them will default to finding information by navigating folders. Give users a search bar, and they’ll just use the search bar.
Example: Yahoo vs Google
Semantic Search is ideal and much more feasible these days with vector databases and LLMs.
But even without them, tags are the solution!
Tags solve multiple problems:
They solve the stress of organization. “Where do I put this file?” Doesn’t matter—flat architecture+ tags and you’re done. No need to worry about it anymore.
Tags allow for context-based meaning. Unlike folders, tags can flexibly work across multiple contexts purely based on how they’re combined with other tags. For example, let’s say you have a single tag called #active. Now you can do this:
#active#client to see all active clients.
#active#projects to see all active projects.
#active#workflows to see all active workflows.
#active#deals to see all active deals.
Then take it a step further with things like #active#deals#midwest to see all information related to dealing with active deals in a midwest region.
Object Tags:#document#note#deal#meeting
Area Tags: #sales#marketing#success#finance#hr
Detail Tags: #hubspot#supered#ios#extension
Status Tags: #backlog#committed#working#testing#done#closed
Special Tags: #hub
And while some folks may argue that using tags can cause just as much chaos as folders…I’ve yet to see that happen. I don’t know why, but people are a bit more thoughtful when it comes to the tags they use.
And besides, even if someone uses a different set of tags than you do—as long as you don’t remove tags, it doesn’t really matter. You can still find what you want and they can find what they want.
Tags work across people regardless of how they think about organization/classification. Folders…do not. One person can (and will) use two seemingly different ways of handling folder hierarchy on any given day or phase of the moon.
And when there are issues that need to be resolved, it’s a hell of a lot easier to merge (even if manually) two tags into one (e.g., #project and #projects than it is to track down and move files…
Log in to comment and vote
Comments2
Skyler Reeves
Jul 1, 2024
This likely warrants two separate feature requests.
Ability to add tags to cards (which is likely a subset of the ability to add metadata to cards).
Ability to have cards live in multiple collections without manual assignment/loading (much more complicated request).
I'm adding my vote to the ability to add tags to cards (and subsequently the ability for end users to see and filter cards in Sidekick or base by tags).
Skyler Reeves
May 21, 2025
Chiming in again to say Tags > Folders with respect to knowledge management.
I’m in that camp that thinks Folders are useful for two things: (1) partitioning information and (2) access control.
Partitioning is already handled in virtue of how Bases work by default. And Access Control is handled through Bases and Share settings.
I have yet to see a company not create absolute fucking bedlam when using folders to organize knowledge—especially when Cards cannot simultaneously live in multiple directories.
The DRY principle inevitably gets violated when information is applicable in multiple contexts but duplicate cards are needed due to access control settings and/or basic user behavior.
Give users folders and a search bar and some percentage of them will default to finding information by navigating folders. Give users a search bar, and they’ll just use the search bar.
Example: Yahoo vs Google
Semantic Search is ideal and much more feasible these days with vector databases and LLMs.
But even without them, tags are the solution!
Tags solve multiple problems:
They solve the stress of organization. “Where do I put this file?” Doesn’t matter—flat architecture+ tags and you’re done. No need to worry about it anymore.
Tags allow for context-based meaning. Unlike folders, tags can flexibly work across multiple contexts purely based on how they’re combined with other tags. For example, let’s say you have a single tag called
#active. Now you can do this:#active#clientto see all active clients.#active#projectsto see all active projects.#active#workflowsto see all active workflows.#active#dealsto see all active deals.Then take it a step further with things like
#active#deals#midwestto see all information related to dealing with active deals in a midwest region.Object Tags:
#document#note#deal#meetingArea Tags:
#sales#marketing#success#finance#hrDetail Tags:
#hubspot#supered#ios#extensionStatus Tags:
#backlog#committed#working#testing#done#closedSpecial Tags:
#hubAnd while some folks may argue that using tags can cause just as much chaos as folders…I’ve yet to see that happen. I don’t know why, but people are a bit more thoughtful when it comes to the tags they use.
And besides, even if someone uses a different set of tags than you do—as long as you don’t remove tags, it doesn’t really matter. You can still find what you want and they can find what they want.
Tags work across people regardless of how they think about organization/classification. Folders…do not. One person can (and will) use two seemingly different ways of handling folder hierarchy on any given day or phase of the moon.
And when there are issues that need to be resolved, it’s a hell of a lot easier to merge (even if manually) two tags into one (e.g.,
#projectand#projectsthan it is to track down and move files…End rant.