If you want a group of users to log into your app to access information or perform an action, then you'll need to create a user role object for that group.
Note: User role objects have all the same options that a regular object has. You can add new fields, set up rules, etc. However, they also allow for users to set up passwords so they can log into your app. Click here to learn more about user roles.
Here are some examples to help you choose the right option for you:
If you have multiple users associated with a single entity, then you'll need to set up a user role object for the users and a regular object for the entities.
For example, let's say you have a list of businesses in your app stored in an object called Clients. Each Client has multiple people working for them that you need to log into the app.
You'll keep your regular Clients object and then create a new, connected Contacts user role object. Each Contact would be connected to the Customer (business) they are working for. This will allow you to show each Contact only the information for their own company and to let them add/edit information only for that company.
Another example of this is when you're tracking employees and their departments in your app. Departments would be a regular object. Employees would be a connected user role object so that employees can log in.
User Role Object Only
If, on the other hand, multiple users can't or won't be associated with a single entity, then you only need a single user role object.
Going back to the Clients example, if each Client is an individual person who needs to access your app, then you would have a single Clients or Customers user role object.
You'll still be able to store any non-user related information about the Client in each record because user role objects have the same options that regular objects do for storing information.