Plunet requires the Plunet API to function with BeLazy. If you do not have it, you can contact your account manager or BeLazy, and Plunet will install it for you with a three-month trial period.


1. Verify BeLazy Connector and API Access

Once you have the BeLazy Connector, verify your access:

  • Log in to Plunet and go to the Admin menu.

  • Select Licenses and scroll down to Plunet Additional Modules.

  • Check if "Plunet API" is enabled. If it is, you can proceed with the BeLazy connection.

It is also beneficial to request Plunet support to enable the Superlock admin user type in your Plunet instance. Normally, Plunet locks orders and items when a user is working on them, even for API operations. The Superlock admin user allows the API to override this restriction. This is safe with BeLazy, as it does not modify or delete information—only adds new orders, items, or jobs.


2. Setting Up the API User

  • Log in to Plunet and navigate to Contacts -> Resources.

  • Click Create New Resource and fill in necessary details (e.g., name).

  • Note down the numerical ID of the newly created resource. You can also see this in the URL.

  • Click the gear icon next to Communication and change:

    • User type to Internal.

    • Resource type to at least Team Member or Project Manager.

  • Click Save and Close.

Next, go to Admin -> Users:

  • Create a new user and enter a Username and Password under Resources (Internal).

  • Select the newly created resource under Resource and choose Plunet API or if you have the Superlock admin, Plunet API (super right) under User Type.

  • Click the + button to add the user.

  • Log out and log in as an Admin user.

Now, go to Admin -> Rights:

  • Locate the newly created user under Resources (Internal).

  • Reset the Rights Group by clicking the blue lock icon.

  • Open the user’s settings and adjust rights (check the Additional information section below).


3. Preparing for BeLazy Connection

When connecting Plunet to BeLazy, you will need:

  • API user credentials (username, password, resource ID).

  • Plunet version (7.4 or later).

  • Translator specialization property (which contains information such as legal, IT, marketing, financial - normally Domain or Area of Expertise/Sector).

    • Go to Admin -> Properties and copy the exact English name of the specialization property.

    • Ensure Resources have access both to this property and to Language (Source).


4. Configuring Plunet for BeLazy Project Creation

4.1 Creating an Order Template for BeLazy

  • Navigate to Admin -> Orders -> Templates.

  • Even if you don’t use order templates, create a new blank template for BeLazy.

  • Note the template number:

    • In Plunet 9 and earlier, after saving the template, select it under Last Selected Templates.

    • The URL will contain a number, which is the order template number.

⚠ Be cautious with templates that include predefined languages. BeLazy cannot overwrite them, which might lead to incorrect project configurations. Preferably do not use languages in your BeLazy templates - BeLazy will add them and select the right price list too.


4.2 File Management Configuration

  • Go to Admin -> Document Templates -> Folder Set.

  • Under Extend Default Folder Set, ensure /Source is added under Items.

    • If missing, add it to ensure BeLazy can create and save files correctly.


4.3 Configuring Workflow Templates

  • Select a Workflow Template to use with BeLazy.

  • In the Description field, enter the job list separated by commas. For example, for a Translation and Editing workflow it should be like this: Translation,Editing. It is case sensitive and each step should include the name of the step.

  • Only workflows with a description will appear in the workflow mapping.

  • If the description field is already in use, add the workflow steps in the first line.

  • Go to Workflow Editor:

    • For each job, click Open Job.

    • Under the Specification tab, find Source Files.

    • Disable Apply Settings from Admin Jobs.

    • Enable /Source folder at the Items Folder Level.

    • ⚠ The Admin Jobs settings do not cover this, so this must be set manually.


Best practices:

  • Create dedicated workflow templates for automation, using prefixes like Automation, BeLazy, or BL.
  • Create a one-step (Translation), a two-step (Translation, Review), and a three-step (Translation, Review, Proofreading) workflow template before starting to configure BeLazy. While your clients may use more steps and then you need to come back and create a new one before moving forward, these three generally cover the steps you need. If you know your clients send you jobs like that, also create a Review one-step workflow, and a Post-editing, Review two-step workflow.
  • Check if prices are assigned to job types in the workflow templates you want to use.


Additional information:

The following is the minimum set of rights you need to give to a Plunet API account to work correctly with BeLazy. Make sure that the user type is Internal and the resource type is Team member.




Checklist

  • Get the API and verify it under Admin -> Licenses -> Plunet API.

  • Obtain the Superlock admin user type from Plunet support.

  • Set up an API user with necessary rights.

  • Record the username, password, and resource ID.

  • Identify the specialization property name and confirm access.

  • Verify that Resources have access to the specialization property and Language (Source).

  • Check that /Source is included in the Extended Default Folder Set.

  • Have an Order Template (preferably blank) and note its number.

  • Verify Workflow Templates include a list of jobs in the Description field.

  • Confirm that Resources have file access in the Workflow Editor.