> For the complete documentation index, see [llms.txt](https://solutions.fundraisingbox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solutions.fundraisingbox.com/additional-resources/additional-permission-set-for-salesforce-standard-objects-and-fields.md). # Additional Permission Set for Salesforce Standard Objects & Fields ### Add Permission set for required permissions for Salesforce standard fields and objects Standard field and object permissions cannot be packaged in Salesforce, so an [additional permission set](https://docs.google.com/spreadsheets/d/1Io2mgIrJjnXvFcmV_E167DqQlHQYHWM_cyGqDuLAccg/edit?gid=0#gid=0) has to be created to allow the Connector user access to all required objects and fields. You can create this manually, but we suggest importing our XML file as documented in the 5 steps below. {% stepper %} {% step %} #### Prepare your environment Ensure the Salesforce CLI is installed. If not, [download it here](https://developer.salesforce.com/tools/sfdxcli). {% endstep %} {% step %} #### Authorize your org sfdx force:auth:web:login -a MyOrgAlias --instance-url {% endstep %} {% step %} #### Create a project (if needed) * sfdx force:project:create -n PermissionSetProject * cd PermissionSetProject Make sure, API version 63.0 or higher is specified in the sfdx-project.json. {% endstep %} {% step %} #### Place the XML file * Create a folder like force-app/main/default/permissionsets/ * Save your permission set XML file there with the .permissionset-meta.xml suffix: force-app/main/default/permissionsets/FundraisingBox\_Connector\_Standard\_Objects.permissionset-meta.xml ```xml true Account.BillingAddress true true Account.Fax true true Account.Phone true true Account.ShippingAddress true true Account.Website true true Campaign.Description true true Campaign.EndDate true true Campaign.ExpectedRevenue true true Campaign.IsActive true true Campaign.StartDate true true Campaign.Status true true Contact.AccountId true true Contact.Birthdate true true Contact.Email true true Contact.Fax true true Contact.HomePhone true true Contact.MailingAddress true true Contact.MobilePhone true true Contact.OtherAddress true true Contact.OtherPhone true true Contact.Phone true true Contact.Title true false true true true true true Account false true true true true true true Campaign false true true true true true true Contact false true true true true true true GiftCommitment false true true true true true true GiftCommitmentSchedule false true false false false true false GiftDesignation false true true true true true true GiftRefund false true true true true true true GiftTransaction false true true true true true true PaymentInstrument false true true true true true false PushTopic true false Account.Business_Account true PersonAccount.PersonAccount true ``` {% endstep %} {% step %} #### Deploy to your Org sf project deploy start --source-dir force-app/main/default/permissionsets/ --target-org MyOrgAlias {% endstep %} {% endstepper %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://solutions.fundraisingbox.com/additional-resources/additional-permission-set-for-salesforce-standard-objects-and-fields.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.