Question about DB Tables for Marketplace Apps

Hey everyone,

I had a (hopefully) quick question about naming tables in your database when you're setting up a marketplace application.

I'm going to have a USERS table, which will store all of the information I collect on sign up and create the account. A user on the account can be a creator, producing items for sale on the platform, but also a customer of other users.

Would I want to create a CUSTOMERS table and a CREATORS (Naming suggestions welcome) table, and have a foreign key on each that is the ID from the USERS table? Or is there a better way to go about this?

I'm trying to figure out a best practice. Ideally something that would be easy to scale, but also easy to work with. For example, I would add an admin dashboard to make it easy to delete users, or troubleshoot issues.