Partner Portal Manual
![](https://storage.crisp.chat/users/helpdesk/website/6a044bcfb3a33800/0c006676-6b0c-4731-a748-e9929c_117lckx.png)
Partner Portal Admin Manual
Partner Admin Terms
Partner Network – All companies, users, and instances under your administrative control from the Partner Portal in CodeBot.
Partner Admin – The named user given the extra Permissions to access the Partner Portal.
Companies- Companies are client organizations. In CodeBot, the company creates a specific environment for users and instances, as well as workspaces and iterations. The Company Environment is 100% self-contained: users, instances, workspaces, and iterations cannot be shared across companies.
Users – Users are consultants that work for the Partner Organization. Or, in some cases, employees on the client side. Users can be added to multiple companies within the Partner Network. Users may even be added to companies from outside the partner network by CodeBot Admins if necessary. These user accounts across multiple companies are totally separate. Users are unable to share workspaces or iterations across companies.
Instances- Instances are Company IDs from SAP SuccessFactors. Each client or partner instance needs to be added to a company individually. Instances are not shared across companies within a Partner Network.
Connectivity Testing – Once a Partner Admin has added an instance, before the instance Is ready for project use, the team must first complete connectivity testing.
Partner Admin Layout
![](https://storage.crisp.chat/users/helpdesk/website/858f86139f0e0000/7aa22aad-80cd-4af2-b321-197c89_2trogz.png)
Execution – Track executions among different Companies and Users in your Partner Network.
Errored – Quickly access all errored executions.
Processing – Quickly access all executions currently being processed.
Companies—Add and edit all companies in your Partner Network.
Users – Add and edit all users (regardless of company) in your Partner Network.
SFSF Configuration – Auto-load a user with the necessary CodeBot Permissions to an instance.
Instances – Add and edit all instances (isolated by company) within your Partner Network.
SSO – Configure SSO for CodeBot.
Permission – Edit user Permissions
Process Steps
When a project starts, the very first thing to do is to add a company.
Adding a Company
Fill out the form on the site.
_(Max Clients and Max Executions can be set to “0” to enable infinite executions and clients)_
Note: Please consult CodeBot before setting a worksheet type to Microsoft 365.
_(Default should be set to Google Sheets for now)._
Company Module Permissions – Grant all permissions possible for any user in this window.
_(Best to include too many options here, then specify permissions at the User Permissions level)._
![](https://storage.crisp.chat/users/helpdesk/website/bb458f0ba8904800/7355076f-27fa-431c-8040-d43bbb_10u8r0a.png)
Adding Instances
Instance Add for General Users Form
Fill in CodeBot Admin section
![](https://storage.crisp.chat/users/helpdesk/website/ccffa0a11787d000/84aad233-35fb-441b-a964-ccb784_bh0fqp.png)
Instance ID = Company ID
Client Secret Key = API KEY (Available via Instance Add Form)
SF User ID – This should be a user that has full permissions. (CodeBot Permissions Document here)
Private Key – pem Certificate encryption key goes here (Available via Instance Add Form
NOTE: Be extra careful to add the instance to the correct company!
Adding Users
General Users – Do not have any admin permissions
Company Admins – Can add new General Users
![](https://storage.crisp.chat/users/helpdesk/website/861b7e8c65a2f800/3a180f85-a5d3-4764-b2a0-734dd3_rqgt5l.png)
Updated on: 22/08/2024
Thank you!