This message was deleted.
# questions
b
This message was deleted.
s
@rhythmic-afternoon-10599 I have quite a lot of experience with this, you don’t necessarily need to merge your tables. • Use different apps, one per persona (has its own pros/cons, sometimes it is the best option) • Use a different Stacker app version (Customer List) to allow different kinds of users from different tables I could dive into this more, but I’m full right now. Don’t hesitate to get in touch on Slack, we could have a quick meeting.
🙌 1
🙌🏻 1
⭐ 1
d
Hi @rhythmic-afternoon-10599: influencers and artists are fundamentally the same thing: people. People who can be influencer, artist or in rare cases even both. For the backend in Airtable, this is a case for a single "people" table (or "contacts") containing a "role" field which is a multi select with values {Influencer, Artist}. For the frontend in Stacker, you can then use the value in "Role" like a record type, i.e. to define which fields to make mandatory. If the workflows and things to do are very different, then 2 apps in Stacker is the best design.