The question is tagged with database and domain-driven-design and the answer is different for these.
From a DDD perspective, it is a bad idea to combine separate concepts into a single concept just because they share some or even all properties. In the domain, what matters is the behavior that the concepts have. If multiple concepts share the exact same behavior, you can consider to merge them into a single concept, as long as the business agrees that it makes sense and you can find a good enough term for it in the ubiquitous language.
In the database, if storing data for separate entities in a single table helps performance, reduce costs, or whatever other reason you may have, then you could consider it. As long as you can map the data back to the domain entities you should be fine. Should you actually do this? Probably not. In practice such optimizations are rarely worth it.