# GUMU™ Portal User
## Registered User
### Connectors Subscription
All the connectors in the portal are available in the Connectors section. In this section, the user can subscribe multiple connector. User need to click on the subscribe button as shown below:
## Dashboard
Once user successfully Logs in GUMU™ account, you will see a Dashboard page as shown below:
The Dashboard screen consists User Profile, summary information about number of **Integration subscribed, Process available in all integration subscribed, Schedule processed** and **Logs.**
The **Total Sync** is a graphical view of the data sync in various integration subscribed.
## Integration
The Integration tab has the list of all connectors subscribed by the user during registration as shown below.
To able to use the connector, user needs to configure the connector. Give the default plugin details, source and target plugin connection details in order to use to connector.
Configuration of GUMU™ Integration connector:
Subscription switch
 Toggle Button on the right top of the connector works as a switch to enable or disable the subscription of the connector. Once you click this, a pop up a message will appear as shown below.
Click on **View More** to go in details of the connector.
### Header Section
**subscription switch** – User can use to Enable and Disable the connector.
**Integration configurator** – In this setting page, user will need to set the default connector setting which will be used by the connector at the time of integration process. This setting defined in this section will be used by the connector to communicate between the 2 system efficiently.
### Integrating Systems
In this section, user will define the connection setting for each system which will be used by the integration to communicate with the system. GUMU™ connectors are built to use the API of the source and target system so that the GUMU™ framework ensures that it communicates only with the business layer and maintain sanity of the systems.
Here, we have given example of Microsoft Dynamics 365 CRM and Sage 100 integration, similar setting will be available for each of the connector subscribed.
#### Connection information
As you can see in the above screenshot both source and target system has icon. On the click of the icon user will be able to entry Connection information for the source and target systems respectively.
You need to enter valid connection information such as Webservice URL, Endpoint Type, User, Password and CompanyID etc, then click on **Test Connection** button to verify Connection details specified.
Important Note: Here please note depending upon the connector subscribed the connection information parameters required will change.
### Synchronization
This section states the various process available in the connector subscribed, the data integration is controlled using action buttons. The processes and its description along with the status of the process can be viewed in the screen as shown below.
#### Show Entries
Here user can control how many process can be viewed in single page. User can change the setting as per the preference. By default the setting is set to 6 entries. User can increase Limit by clicking on dropdown. It will provide four options 3, 6, 9,12 and 15.
#### Search
Search functionality for quick search of the processes by keys you provide in search box.
#### Start Action
 This button enables user to start the particular Integration process manually on demand. When you start the integration process, Status will change from Idle to Running and once process completed it will change from Running to Idle.
#### Stop Action
This button appears after you click start, is used to stop the integration manually on demand.
#### Schedule Action
This button will allow user to set Schedule for the process. Schedule can be set in four types like Daily (Once), Daily (Every), Weekly and Monthly.
**Daily (Once)**
Click on ‘**Choose OccursAt**’ this will show a clock to set a time for schedule. Once the time is selected, click ok.
Then click **Submit** Button to save the schedule. It will popup message as follows.
**Daily (Every)**
On Click of **Daily (Every)** user will be able to set ‘**Occurs Every (Hours)**’. In this textbox user needs to provide time frequency for executing process in the given start time and end time. Click on choose **StartTime** and choose **EndTime** will show clock then we select time to set schedule and click Ok.
Then Click on **Submit** to save Schedule then Popup for success message appears.
**Weekly**
When user click on **Weekly** select Days of week and choose time by clicking on ‘**Choose OccursAt**’. It will show Clock to set time click Ok.
Then click on **Submit** button to save schedule.
**Monthly**
If you click on **Monthly** set Time by clicking on ‘**Choose OccursAt**’. It will show Clock select Time and Press Ok.
Click on **Submit** Button to Save Schedule.
#### Process task
This icon will show view entity mapping. Click on View entity mapping will show following screen. The process task depends on the connector subscribed by the user, this changes connector to connector.
#### Control Process
This button is used to enable or disable each process individually.
#### Refresh
Click on Refresh to see all the logs generated during the time of running. Process it update the process status and last sync date/time.
---
# Agent Instructions: 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:
```
GET https://docs.greytrix.com/gumu-cloud-integrations/gumu-portal-user.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.