Profiles in CANDID define a user’s baseline access across the platform. Every user must have exactly one Profile, which sets the foundation for what they can see (objects, fields, tabs) and do (create, edit, delete, run reports).
Think of Profiles as the “driver’s license” for the system—they establish the default level of permission before any extra access (like Permission Sets) is added.
Profiles are the backbone of CANDID’s security and access model. They ensure consistency and control by enforcing what different types of users—LO, Admins, Recruiters, or LOAs—can and cannot do inside the platform.
💡 Tip: Use Profiles to enforce role-based access control. Keep them broad and consistent, then layer exceptions with Permission Sets.
Profiles act as the mandatory baseline access layer in CANDID.
⚠️ Best Practice: Don’t over-customize Profiles. Keep them lean (one per main role type), and avoid creating dozens of variations.
Profiles are critical because they establish the minimum access every user needs to do their job. Without them, access would be inconsistent and security would be difficult to enforce.
By using Profiles effectively, CANDID admins can: