--- documentId: "THIRD-PARTY_PLUGIN_DEVELOPER_ONBOARDING_AND_PUBLISHING_GUIDE" title: "Third Party Plugin Onboarding and Publishing Guide" version: "v08" publisher: "Gamanet" author: "Marian Gal" datePublished: "" dateModified: "2026-10-22" effectiveFrom: "" effectiveTo: "" applicableProduct: "portal-services" applicableProductModule: "" applicableProductVersions: [] documentType: "OVR" audience: ["developer"] language: "en" confidentiality: "public" abstract: "A guide for third-party C4 plugin Developers and company representatives covering company registration and contract signing in Contract Web, required Edu training, and role assignments. It explains plugin registration, customer visibility, Developer invitations, version uploads, optional testing, and publication in Plugin Store." keywords: ["C4","third-party plugins","Contract Web","Plugin Store","onboarding","publishing","Edu training","Contract Manager","Legal Representative","Development Manager","Plugin Admin","Developer","QA Tester"] licenseOrUsageTerms: "" canonicalUrl: "https://my.c4portal.com/Atlas/docs/THIRD-PARTY_PLUGIN_DEVELOPER_ONBOARDING_AND_PUBLISHING_GUIDE/latest/index.html" downloadFormats: ["HTML","PDF","Markdown"] fileChecksum: "9fF14dtxV2YE170YiAywrIZsqt3Yd1i\u002BHBXzSrMcIaw= " citationText: "" --- [Skip to document](#gmn-main) | **GAMANET** | | --- | **Third-Party Plugin Developer Onboarding and Publishing Guide** Contract Web and Plugin Store procedures for Developers and company representatives **Document type** User guide **Document reference** Not assigned | System C4 | Contract Web and Plugin Store **Document owner** Gamanet **Prepared by** Hana Klikáčová **Version and issue date** v08 | 22 October 2026 **Prepared for** Third-party plugin Developers and company representatives **Classification** Not classified # Contents 1. [1. Introduction](#introduction) 2. [2. Sign the Contract](#sign-the-contract) 3. [3. Publish the Plugin](#publish-the-plugin) # 1. **Introduction** Portal Services by Gamanet brings together the online services that support your work with the C4 System—from deployment and licensing to updates, development, training, and maintenance. Whether you are a Developer, engineer, end user, or business partner, Portal Services helps you access the tools and services you need. This guide walks you through becoming a Third-party Plugin Developer, from signing your company’s contract to publishing your Plugin. ## **Portal services, roles and Edu training** Use Contract Web to sign contracts, download certificates, and manage your company’s team and roles. Use Plugin Store to manage C4 extensions and applications that run within C4 Simple Client, including third-party Plugins. Each role gives you access to specific actions in Portal Services. You can hold multiple roles to access all the actions you need. | **Role** | **Portal service** | **Required Edu training** | | --- | --- | --- | | Contract Manager | Contract Web | Third Party Plugin Development | | Legal Representative | Contract Web | - | | Development Manager/ Plugin Admin | Plugin Store | Third Party Plugin Development | | Developer | Plugin Store | Developer | | QA Tester | Plugin Store | - | \*The Development Manager role is assigned in Contract Web. Plugin Admin permissions are granted in Plugin Store. ![](media/image1.jpg) # 2. **Sign the Contract** Gamanet works solely with legal entities or companies with which it signs contracts. This person or company then guarantee the quality of the code and accepts full responsibility for any damages caused by it. ## **Assign a Contract Manager** Before the contract signing process, it is important to define a specific person who will manage the contract between the Third-party company and Gamanet. That person becomes a Contract Manager for the company on the C4 Contract Web platform and gains access to a range of key features, including: - Setting up and managing company account - Overseeing the entire contract signing process - Inviting the Legal Representative to review and sign contracts - Updating your company’s Legal Representative when needed - Adding employees and assigning them appropriate roles, such as the Development Manager role, which is responsible for managing Plugins in the Plugin Store - And much more to ensure smooth cooperation. ## **Log in to the Contract Web** To get started, the Contract Manager opens Contract Web at: [https://my.c4portal.com/contract](https://my.c4portal.com/contract). ![](media/image2.png) The user clicks on **Login** in the upper-right corner or on **Register** button which is part of the Landing page. An OAuth page appears where the user can create a new account using email, phone number with a country code, and password, or log in to an existing account. The registration process includes email verification and number verification. After completing account registration, the user is automatically assigned the role of Contract Manager (without any prior invitation, contact, or engagement with Contract Web). The user is then redirected to the Contract Web welcome page, where all relevant information about the Contract Manager role is displayed. ![](media/image3.png) At the bottom of the page, there is an orange **Continue** button. Once clicked, the user gains full access to the Contract Web user interface. ## **Register your company** After the **Continue**, click **Register** in the upper-right corner and enter your company’s details. Complete the required information: - Profile: Name- Company or legal entity name, Street- Street address, ZIP- Postal/ZIP code, City- City or town - Payment: Corporate ID- Company registration number, Tax ID- Taxpayer identification number, VAT ID- VAT registration number, VAT is applicable and cannot be decline, Bank account (IBAN)- Company bank account details in IBAN format. ![](media/image4.png) After completing all required fields, clicks **Save**. At this moment, Contract Manager gain access to the **Contracts** section. ## **Create a Contract** In the **Contracts** tab located in the left navigation column, the Contract Manager can create a new contract by clicking on **New Contract** button. ![](media/image5.png) Choose the agreement you need from the available templates: - Business Partner - Plugin Developer To develop and distribute Plugins, select Plugin Developer and follow the guided steps. Before proceeding, the selected contract template can be previewed in the left corner of the screen. This allows the user to carefully review all contract details and ensure that the information is accurate and complete. This step represents the final opportunity to make any changes. Once the **Next** button is clicked and the contract is submitted no further edits are possible. ## **Edu Training Validation** Before the sign is possible, the system checks whether the Contract Manager has valid Edu training. For the Plugin Developer contract, the required course is Third Party Plugin Development. If the training is expired or not yet completed, a reminder appears. Click **Continue** and complete the training. Assigning the completed course to the person can take up 5 minutes. If the training is valid, the process continues automatically. ## **Invite the Legal Representative and sign the contract** The next step is assigning the Legal Representative for the company. The Contract Manager can invite them by filling in their email address and sending an invitation email. They will receive an email with a link valid for 2 weeks. They must click the link and log in or register via OAuth, as required for all Portal Services users. After logging in, they automatically become Legal Representative (the role assigning process takes up to 5 min). They can then review the contract and click **Sign** in the upper-right corner. ![](media/image6.png) Once the Legal Representative signs, the contract is sent to Gamanet for signature. After both parties have signed, the Contract Manager and Legal Representative receive the valid contract by email in PDF format. Your company is now a Gamanet partner. # 3. **Publish the Plugin** ## **Assign a Development Manager** Choose the person who will be responsible for managing your company’s Plugins. In Contract Web, this role is called Development Manager. Once your company has an active, valid contract, the Contract Manager can invite this person as an employee. Open **Employees** in the left-hand menu and click **Add employee** in the upper-right corner. Select the **Development Manager** role, enter the person’s email address, and send the invitation. ![](media/image7.png) The invitation link is valid for 2 weeks. To accept, the invited person opens the link and logs in or creates an account. Once they accept the invitation, they are assigned the Development Manager role. This takes at least 5 minutes, during which access may be temporarily limited. When they log in to Plugin Store [https://my.c4portal.com/pluginstore/Public/User/Home](https://my.c4portal.com/pluginstore/Public/User/Home), the system automatically checks whether they have valid Third Party Plugin Development Edu training. If the training is valid, the system grants them Plugin Admin permissions. After that they can manage your company’s Plugins. ## **Register your Plugin** Plugin Admin will see a **User** item in the top menu, which allows them to manage the Plugins developed by Developers for the company they represent. This means they can register Plugins and manage their entire lifecycle—from initial deployment into the system, through management of support and warranty settings, overseeing the new versions to their deactivation. To register a Plugin, click **New Plugin** in the upper right corner and complete the required information. ![](media/image8.png) Pay particular attention to these fields: - **Plugin category**, **Owner of Plugin** and **Price:** check that each value is correct. - **Plugin additional info description:** this appears on the public Plugin Store page. Use it to explain what your Plugin does and how it helps customers. - **Plugin Policies:** select the support and warranty settings that apply to your Plugin. If your support or warranty settings differ, define them in **Plugin Policy** in the left-hand menu after registration. These settings appear on the Plugin’s details page for customers to review. - **Visibility:** in the **Plugin Policies** section, choose **Public** to make the Plugin visible to everyone, or **Specific customers** to make it visible only to selected customers. - **Certification is required:** Define if you wish to undergo certification process in the future. - **Testing requirement:** choose whether testing is required before publishing, based on your company’s needs. Plugins that have not been tested are labelled **Untested**. The Plugin Admin can update the Plugin information throughout its lifecycle. ### **Invite specific customers** If you select Specific customers under Visibility, a **Plugin Access** section appears in the left-hand menu after you save the Plugin information. Open **Plugin Access** and click **Invite** to invite a customer. They receive an email invitation, which they need to accept within 2 weeks to access the Plugin. ![](media/image9.png) Once the customer accepts the invitation and the Plugin is published, they can download it from Plugin Store public page. ## **Invite the Developer** After saving the Plugin information, the Plugin Admin must invite the Developer who will upload the Plugin to Plugin Store. Plugin Admin invites Developers who develop the Plugin and have a contractual relationship with the company represented by the Plugin Admin. In the **Participants** section, use the orange **Invite** button. ![](media/image10.png) The invited person receives an email with an invitation link valid for 2 weeks. To accept, they open the link and log in or create an account. After accepting the invitation and logging in, they are automatically assigned the Developer role and gain access to the Plugin in the Plugin Store. ## **Upload the Plugin** The Developer can upload the Plugin to Plugin Store only with valid Developer Edu training. If it is missing, the system automatically displays a notification with a link to the course in question. Once logged in to the Plugin Store, the Developer needs to go into **Plugin versions** in the left-hand menu. Click **Upload New Version** in the upper-right corner and follow the steps to upload the Plugin. ![](media/image11.png) The Developer can upload new versions but cannot edit the Plugin’s details. Once the upload is complete, the Plugin Admin receives an email notification. ## **Test the Plugin** If testing is required for the publishing, the Plugin Admin must invite a QA Tester in the Participants section. The Plugin Admin then sends the QA Tester a test license key. It is available in the **Test Licenses** in the left-hand menu, selects the **QA Tester** from the invited participants and click **Send to selected**. The key is valid for 2 weeks and can be resent if needed. ![](media/image12.png) The QA Tester receives two emails: an invitation to test the Plugin and separate email with the test license key. Once they accept the invitation, they can access the Plugin and begin testing. After successful testing, the QA Tester can mark the Plugin as tested with permission granted by the Plugin Admin in **Details of Plugin**. Otherwise, they notify the Plugin Admin to mark it as tested. ![](media/image13.png) ## **Publish the Plugin** Once testing is complete—or if testing is not required—the Plugin is ready to be published, either publicly or for a specific customer. Only the Plugin Admin can publish the Plugin. To do so, open the Plugin Details page and click **Publish** in the upper-right corner, above the Plugin information. ![](media/image14.png) **Now your Plugin has been successfully published!**