The CRModular interface is currently in Turkish. Menu and button names are shown in bold Turkish with an English explanation in brackets.
Permissions are managed under Ayarlar → Güvenlik (Settings → Security). We recommend this order.
1. Role hierarchy
Build your org chart, for example General Manager → Sales Director → Regional Manager → Rep. A higher role sees the records of the roles below it. Give managers the Tüm Verileri Görüntüle (View all data) flag if needed.
2. Profiles
Create profiles such as Sales Rep, Sales Manager and Support Agent. In each profile’s object permission matrix, tick per object: read, create, edit, delete, view all, modify all.
Example: give reps read, create and edit on opportunities but not delete or view all. Reps then see only their own opportunities and those of people below them in the hierarchy.
3. Permission sets
Extra rights on top of a profile for exceptions, such as “bulk data export”.
4. Adding users
Kullanıcılar → Yeni Kullanıcı (Users → New user): username, email, first and last name, temporary password, access role and organisation role. Then assign a profile and, if needed, a permission set. A user signing in with a temporary password must change it at first sign-in.
If your plan’s user limit is reached, you cannot add users; deactivate users or upgrade your plan.
5. Sharing rules (optional)
Open specific records to other teams with owner-based or criteria-based rules.
Important: a user without a profile behaves as fully privileged for backwards compatibility. Assign every user a profile before going live.
Check
Sign in as a rep: they should see only their own and their team’s records, and menus they have no access to should be hidden.