Feedback Management
User Management
Learn how to manage users and their attributes in your encatch project
Users in encatch are your application users (end users) who interact with your application and provide feedback.
Understanding Users vs Members
- Users: End users of your application who submit feedback. Your users can scoped to the project level. Therefore, same user in two projects are counted as two different users.
- Members: Administrators who manage the project and have access to the portal.
User Attributes
You can configure users atrributes like email, department, role, etc. to help you filter and analyze feedback data. User attributes are broken into 3 types
Pre-configured attributes: Attributes that are pre-defined by you, that are filterable in the portal.
- Examples include: email, department, role, etc.
Dynamic attributes: Attributes that are not planned in advance and are created on the fly from your code.
- Examples include: custom attributes, traits, etc.
System attributes: Attributes that are pre-defined by the system and are not editable by you.
- Examples include: user_name, last_seen, first_seen, created_at, updated_at, etc.
Manage Users
You can manage (create, view,edit,delete) users in the portal.
- Individually
- Bulk upload
- Sync from your backend using API keys (Comming soon)
Important Notes
- user_name field should be unique for each user in the project.
- When chosing to create a user from SDK, ensure that this field is not easily guessable or reproducible.
- Only configure user fields which are useful for you to create filters and segments in the portal.
- To protect users information, the API SDK cannot send back the user fields to your frontend application. Unless explicitly configured to show certain fields where dynamic attribute of users data is shown in your form. Example, a question like, "How has {{user_f_name}} been expereincing the app?"
How is this guide?