ed727
4
The User datatype is a special datatype that has functions like login, password, etc. I don’t believe you can create a second and separate user datatype, since it wouldn’t have those special functions.
If the “company” user does not need to login, then it does not need to be a User datatype. But if it does – for example if you want a company-wide login and password, then it would need to be a User datatype.
If I had two different types of users and both required logins and other functions that only the User datatype can provide, I would work with the User datatype for both, but set it up in one of the below ways:
- Create the fields needed for each type within the User datatype. Some fields will be blank if they don’t apply to the specific user, but it doesn’t matter. In your input and display, when you are showing one type of user, you can set it up to only show the fields related to that user.
- You can create Company and Staff datatypes in addition to a central User datatype. Then link each User entry to its corresponding entry for Company and Staff. This is a little more complex however because now you have three datatypes.
In my app I have a few different types of users, but they are all combined in the User datatype. I identify what type of user they are with “yes/no” fields and that also flows through to the privacy settings so I can control what users have access to.