[go: up one dir, main page]

0% found this document useful (0 votes)
10 views3 pages

P Admin Notes

In Salesforce, profiles define user permissions and access to objects, fields, and features, with standard and custom profiles available. Users can manage visibility of standard fields and objects but cannot delete them, while various text data types are provided for different use cases. Key permissions like 'View All' and 'Modify All' allow extensive access to records, and users can be deactivated through the Setup menu by an administrator.

Uploaded by

polisatya79815
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views3 pages

P Admin Notes

In Salesforce, profiles define user permissions and access to objects, fields, and features, with standard and custom profiles available. Users can manage visibility of standard fields and objects but cannot delete them, while various text data types are provided for different use cases. Key permissions like 'View All' and 'Modify All' allow extensive access to records, and users can be deactivated through the Setup menu by an administrator.

Uploaded by

polisatya79815
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

In Salesforce, a profile defines a user's default permissions within the organization.

It controls what a user


can do, such as accessing specific objects, fields, tabs, and other features. Profiles determine what users
can see and interact with in the Salesforce application.
Here's a more detailed explanation:
 Permissions:
Profiles grant or restrict users' access to various aspects of Salesforce, like object permissions (read, edit,
delete), field-level security, tab visibility, and app access.
 Standard vs. Custom:
Salesforce provides standard profiles (like "Standard User" or "System Administrator") and allows users to
create custom profiles tailored to specific business needs.
 User Access:
A user's profile, along with their license, dictates what they can do in Salesforce.
 Roles and Permission Sets:
Profiles are often used in conjunction with Salesforce roles and permission sets to manage access
effectively. Roles typically determine access based on record ownership, while permission sets can add
specific permissions to a profile.
In Salesforce, you cannot permanently delete standard objects or standard fields because they are
part of the core platform. However, you can hide or remove them from certain interfaces to reduce
clutter. Here’s what you can do:
For Standard Fields:
1. Remove from Page Layouts – You can exclude standard fields from Page Layouts, making them
invisible to users in the UI.
2. Set Field-Level Security (FLS) – Under Setup > Object Manager > [Object] > Fields &
Relationships, you can restrict field access by profile.
3. Use Lightning App Builder – In Lightning Experience, you can control field visibility in Record
Pages.
4. Rename or Label Override – You can change the display label of a standard field (but not its API
name).
For Standard Objects:
 You cannot delete standard objects (e.g., Account, Contact, Opportunity).
 You can hide them from the App Navigation by modifying:
o App Settings (Setup > App Manager > Edit App)
o Profile/Object Permissions (Setup > Profiles > [Profile] > Object Settings)
Exceptions:
 Some standard fields (like "Created By" or "Last Modified Date") are system fields and cannot
be removed from layouts.
 Certain standard objects (e.g., Tasks, Events, Notes) can be hidden but not deleted.
Alternative: Use Custom Objects Instead
If a standard object/field isn’t needed, consider using custom objects/fields that you can fully control
(create, modify, or delete).
Would you like help with a specific standard field or object? Let me know!
n Salesforce, text data types are used to store alphanumeric characters, strings, and other text-based
information. Here’s a breakdown of the available text field types and their use cases:
1. Text
 Description: Stores a single line of text (up to 255 characters).
 Use Case: Short text entries like names, labels, or codes.
 Example:
Field Name: "Product Code" | Max Length: 50
2. Text Area
 Description: A multi-line plain text field (up to 255 characters).
 Use Case: Brief descriptions, comments, or notes.
 Example:
Field Name: "Quick Notes" | Visible Lines: 3
3. Text Area (Rich)
 Description: Supports formatted text (bold, italics, hyperlinks) and images (up to 32,768
characters).
 Use Case: Detailed descriptions, email templates, or rich content.
 Example:
Field Name: "Product Description" | Toolbar: Basic formatting options
4. Text Area (Long)
 Description: Plain text with a large capacity (32,768 characters).
 Use Case: Long paragraphs, logs, or JSON/XML data.
 Example:
Field Name: "Error Log" | Visible Lines: 10
5. Text Area (Encrypted)
 Description: Stores sensitive text data (like passwords or API keys) with encryption.
 Use Case: Secure storage of confidential information.
 Example:
Field Name: "API Key" | Mask Type: "All Characters"
6. URL
 Description: Validates and stores web addresses (up to 255 chars).
 Use Case: Links to websites, documents, or resources.
 Example:
Field Name: "Company Website" | Format: https://example.com
7. Email
 Description: Validates email format (up to 80 chars by default, extendable to 255).
 Use Case: Email addresses for contacts, leads, or users.
 Example:
Field Name: "Support Email" | Unique: Yes
8. Phone
 Description: Optimized for phone numbers (formatted display, but stored as text).
 Use Case: Business or mobile phone numbers.
 Example:
Field Name: "Work Phone" | Format: (123) 456-7890
Key Considerations:
 Character Limits: Be mindful of the max length (e.g., 255 vs. 32,768).
 Encryption: Use Text Area (Encrypted) for sensitive data (requires Shield Platform Encryption for
full security).
 Rich Text: Supports HTML but is not searchable in standard SOSL queries.
 Validation: Use Validation Rules or Flow to enforce formats (e.g., URL/Email).
When to Use Which?
Max
Data Type Best For
Length

Text Short codes, names 255 chars

Text Area Multi-line comments 255 chars

Text Area Formatted descriptions 32,768


(Rich) (HTML/images) chars

Text Area 32,768


Large plain text (logs, JSON)
(Long) chars

URL/Email/ Validated web/email/phone


255 chars
Phone formats

Renaming standard fields in standard objects depends on the platform you're using. Here are instructions
for common CRM and database systems:
In Salesforce
1. Navigate to Setup:
o Click the gear icon → Setup
2. Access Object Manager:
o In the Quick Find box, type "Object Manager" and select it
3. Select the Standard Object:
o Click on the standard object (e.g., Account, Contact, Opportunity)
4. View Fields & Relationships:
o Click "Fields & Relationships" in the left sidebar
5. Rename the Field:
o Find the standard field you want to rename
o Click the field label (not the API name)
o Edit the label and click Save
Note: Not all standard fields can be renamed in Salesforce, and renaming may affect integrations or
reports.
Understanding "View All" and "Modify All" Permissions in Salesforce Profiles
These are two powerful object-level permissions in Salesforce that control record visibility and editing
capabilities beyond normal sharing rules.
View All Permission
What it does:
 Allows users to view all records of the specified object regardless of sharing settings
 Overrides all organization-wide defaults (OWD), role hierarchies, sharing rules, manual shares, and
team settings
 Does not grant edit/delete permissions
Modify All Permission
What it does:
 Allows users to view, edit, and delete all records of the specified object
 Includes all capabilities of "View All" plus full edit/delete rights
 Overrides all sharing settings (OWD, role hierarchy, etc.)
Key characteristics:
 Provides complete CRUD (Create, Read, Update, Delete) access
 Still respects field-level security (unless "Edit" permission is also granted)
 Should be granted sparingly due to its power
How to Deactivate a User in Salesforce
There are several methods to deactivate a user in Salesforce, depending on your needs and permissions.
Here's a comprehensive guide:
Method 1: From Setup (Admin Access Required)
1. Log in to Salesforce with System Administrator privileges
2. Click the Setup (gear) icon → Setup
3. In the Quick Find box, type "Users" and select Users
4. Locate the user you want to deactivate (use search/filters if needed)
5. Click the user's name to open their record
6. Click Edit
7. Uncheck the Active checkbox
8. Click Save

You might also like