[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cms-entry-help-users-roles-and-permissions-en":3},{"message":4,"data":5,"success":40},"OK",{"id":6,"entry_type":7,"locale":8,"slug":9,"title":10,"summary":11,"body":12,"blocks":13,"author_name":14,"published_at":15,"updated_at":15,"data":16,"category":14,"tags":17,"related":18,"alternates":31,"seo":36,"cover":14,"media":39,"preview":38},27,"help","en","users-roles-and-permissions","Users, Roles and Permissions","Use the role hierarchy, profiles, permission sets and sharing rules to decide who can see and edit which records.","> The CRModular interface is currently in Turkish. Menu and button names are shown in **bold Turkish** with an English explanation in brackets.\n\nPermissions are managed under **Ayarlar → Güvenlik** (Settings → Security). We recommend this order.\n\n## 1. Role hierarchy\n\nBuild 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.\n\n## 2. Profiles\n\nCreate 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.\n\nExample: 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.\n\n## 3. Permission sets\n\nExtra rights on top of a profile for exceptions, such as \"bulk data export\".\n\n## 4. Adding users\n\n**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.\n\n> If your plan's user limit is reached, you cannot add users; deactivate users or upgrade your plan.\n\n## 5. Sharing rules (optional)\n\nOpen specific records to other teams with owner-based or criteria-based rules.\n\n> **Important:** a user without a profile behaves as fully privileged for backwards compatibility. Assign every user a profile before going live.\n\n## Check\n\nSign 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.\n",[],null,"2026-10-03T17:31:33.463Z",{},[],[19,23,27],{"slug":20,"title":21,"summary":22,"entry_type":7},"getting-started-setup-guide","Getting Started: Set Up Your Account Step by Step","From sign-up to go-live: a starter guide to which settings to configure in which order, and how to check each step.",{"slug":24,"title":25,"summary":26,"entry_type":7},"company-settings-and-security","Company Settings and Security (Including Two-Factor Authentication)","Set time zone, currency, password policy, session timeout and two-factor authentication, and reset 2FA for a user who lost their phone.",{"slug":28,"title":29,"summary":30,"entry_type":7},"sales-process-stages-and-reasons","Sales Process: Stages, Required Steps and Win\u002FLoss Reasons","Set up opportunity stages, sales path guidance, win\u002Floss reasons and territory-based automatic assignment.",[32,33],{"locale":8,"slug":9},{"locale":34,"slug":35},"tr","kullanici-rol-ve-yetki-yonetimi",{"title":37,"description":11,"canonical_url":14,"noindex":38,"og_image":14},"Users, Roles and Permissions | CRModular Help",false,{},true]