Reference
Permissions, statuses, and what CRM does automatically.
7 articles shown
- Activities and Relationships Through the API
What you can do with activities and relationships by calling the CRM API directly, beyond what the Console offers, including reading a single record by its ID, running many changes in one request, and how loosely the API checks an activity's owner.
- What a Contact Merge Moves
A reference for what happens, application by application, when you merge a duplicate contact away — which records simply move to the surviving contact, which ones combine instead, and what stays behind.
- Contact Data Available Only Through the API
Contact abilities with no Console or Portal screen behind them, reachable only by calling the CRM API directly, including linking spouses, finding a contact by a secondary email address or by number, and finding who named a contact as their Portal delegate.
- Access the CRM API
The single public address that reaches every CRM service, and where to read the API's documentation without signing in.
- CRM Permissions Reference
The four ready-made CRM permission levels, which pages need a specific permission to open, which ones are open to any signed-in staff member, and how a grant can be narrowed to records connected to a particular organization.
- CRM Blocks for Portal Pages
The CRM elements available when building Portal pages, including the five self-service blocks in the page designer, the Contact Profile card for Account Home, and the feature bundles that place them for you.
- System Engagement Metrics
What each built-in engagement metric measures, from years of membership to committee seats, event registrations, gifts, and merchandise purchases, so you know what you are choosing when you build a scoring model.