UNPKG

sf-agent-framework

Version:

AI Agent Orchestration Framework for Salesforce Development - Two-phase architecture with 70% context reduction

322 lines (250 loc) 6.88 kB
# Organization Setup Task This task guides the initial setup and configuration of a Salesforce organization following best practices. ## Purpose Enable administrators to: - Configure new orgs properly - Establish security foundation - Set up core features - Implement governance - Prepare for development ## Setup Phases ### Phase 1: Foundation Setup **1.1 Company Information** ```yaml Setup Steps: 1. Setup Company Settings Company Information 2. Configure: - Organization Name - Default Locale - Default Language - Default Time Zone - Currency Settings - Fiscal Year 3. Setup Company Settings Business Hours 4. Define standard business hours ``` **1.2 Security Settings** ```yaml Password Policies: - Minimum length: 12 characters - Complexity: Numbers, letters, special chars - Password history: 12 - Expiration: 90 days - Lockout attempts: 5 Session Settings: - Timeout: 2 hours - Lock sessions to IP: Yes - Force relogin after timeout: Yes - Require secure connections: Yes Login Access Policies: - Administrators can log in as users: 48 hours - Require approval for login-as - IP restrictions for admins ``` ### Phase 2: User Management **2.1 Role Hierarchy** ```yaml Structure: CEO ├── VP Sales ├── Sales Manager East └── Sales Rep East └── Sales Manager West └── Sales Rep West ├── VP Service └── Service Manager └── Service Rep └── VP Operations └── System Administrator ``` **2.2 Profiles and Permission Sets** ```yaml Minimum Access Profile: - Clone from: Minimum Access - Salesforce - Remove all object permissions - Use as base for all users Permission Set Strategy: Base_Sales_Access: - Read: Account, Contact, Opportunity - Create/Edit: Opportunity, Task, Event Base_Service_Access: - Read: Account, Contact, Case - Create/Edit: Case, Task System_Configuration: - Manage Users - Customize Application - View Setup and Configuration ``` ### Phase 3: Data Model Setup **3.1 Standard Objects Configuration** ```yaml Account: - Enable Account Teams - Configure Account Hierarchy - Set up Record Types: - Customer - Prospect - Partner - Page Layouts per Record Type Opportunity: - Configure Sales Process - Set up Stages: - Prospecting (10%) - Qualification (20%) - Needs Analysis (40%) - Proposal (60%) - Negotiation (80%) - Closed Won (100%) - Closed Lost (0%) - Enable Opportunity Teams Case: - Configure Support Process - Set up Status Values: - New - Working - Escalated - Closed - Enable Case Assignment Rules ``` **3.2 Custom Objects** ```yaml Naming Convention: - API Name: BusinessFunction_ObjectPurpose__c - Label: Clear business name - Plural: Grammatically correct Example: API Name: Sales_Territory__c Label: Sales Territory Plural: Sales Territories Fields: - Name (Auto-number: TER-{00000}) - Region__c (Picklist) - Manager__c (Lookup to User) - Target_Revenue__c (Currency) ``` ### Phase 4: Automation Setup **4.1 Email Configuration** ```yaml Organization-Wide Addresses: - noreply@company.com - support@company.com - sales@company.com Email Deliverability: - Access Level: All Email - Enable bounce management - Configure SPF records - Set up DKIM Email Templates: - Folder structure by department - Standard templates: - Welcome email - Case confirmation - Password reset ``` **4.2 Process Automation** ```yaml Approval Processes: - Opportunity Discount Approval - Entry Criteria: Discount > 20% - Approver: Manager - Actions: Email notification, Field update Flow Strategy: - One Flow per object - Before-save for field updates - After-save for related records - Scheduled for batch operations ``` ### Phase 5: Integration Setup **5.1 Connected Apps** ```yaml API Integration App: - OAuth Scopes: - Access and manage data (api) - Perform requests at any time (refresh_token) - IP Restrictions: Whitelist only - User Restrictions: Integration user only Mobile App: - OAuth Scopes: - Access and manage data (api) - Access unique user identifiers (openid) - Session timeout: 2 hours - PIN protection required ``` **5.2 Integration User** ```yaml Setup: - Username: integration@company.com - Profile: Integration User Profile - Permission Sets: - API_Enabled - Specific object access - Password never expires - API only access ``` ### Phase 6: Analytics Setup **6.1 Reports and Dashboards** ```yaml Folder Structure: ├── Executive Dashboards ├── Sales Reports ├── Pipeline Reports ├── Forecast Reports └── Activity Reports ├── Service Reports ├── Case Reports └── SLA Reports └── Administrative Reports Standard Dashboards: - Executive Overview - Sales Performance - Service Metrics - User Adoption ``` ### Phase 7: Compliance Setup **7.1 Field History Tracking** ```yaml Enable for: - Account: All financial fields - Opportunity: Stage, Amount, Close Date - Case: Status, Priority, Owner - Custom Objects: Key fields Retention: - Standard: 18 months - Archive older data ``` **7.2 Audit Trail** ```yaml Setup Audit Trail: - Download monthly - Store securely - Retain for 7 years Field Audit Trail: - Enable for sensitive objects - Configure retention policy ``` ## Configuration Checklist ### Security - [ ] Password policies configured - [ ] Session settings secured - [ ] IP restrictions enabled - [ ] MFA enabled for all users - [ ] Login hours set ### Users - [ ] Role hierarchy created - [ ] Profiles minimized - [ ] Permission sets created - [ ] Admin users < 5% of total ### Data Model - [ ] Standard objects configured - [ ] Record types created - [ ] Page layouts optimized - [ ] Validation rules added ### Automation - [ ] Email deliverability configured - [ ] Approval processes created - [ ] Flows documented - [ ] No workflow rules created ### Integration - [ ] Connected apps secured - [ ] Integration user created - [ ] API limits monitored - [ ] Error handling configured ### Analytics - [ ] Report folders organized - [ ] Standard reports created - [ ] Dashboards deployed - [ ] Subscriptions configured ### Compliance - [ ] History tracking enabled - [ ] Audit trail configured - [ ] Data retention defined - [ ] Compliance documented ## Success Criteria All security measures enabled User access model defined Core objects configured Basic automation working Integration ready Reports available Compliance met Documentation complete