Hi,
This is a complex use case... Let me give you a generic answer and I'll follow up with a sample in the Forge.
1. You need to create the logic for that over the system APIs that manage Users. This means creating a record in the User entity.
2. You have to model this as a 1-to-1 relationship. You can see how to do it in this lesson.
3. This really depends on what you want to do. You can add a UserId attribute to the entities you want to protected the access and when you fetch information from those entities use the Session.UserId to create a filter.
Stay tuned, I'll follow up with a complete sample on the Forge.
Cheers
This is a complex use case... Let me give you a generic answer and I'll follow up with a sample in the Forge.
1. You need to create the logic for that over the system APIs that manage Users. This means creating a record in the User entity.
2. You have to model this as a 1-to-1 relationship. You can see how to do it in this lesson.
3. This really depends on what you want to do. You can add a UserId attribute to the entities you want to protected the access and when you fetch information from those entities use the Session.UserId to create a filter.
Stay tuned, I'll follow up with a complete sample on the Forge.
Cheers