There are different ways to import your users into COYO. We’ll show you the advantages and disadvantages of the individual options here.
To find out what to do, please read the following articles:
Create local users within COYO
Within COYO, there’s a simple and intuitive way to invite new users:
In Administration, you have the opportunity to create what are known as local users.
These users are only saved in your COYO environment and otherwise have no connection to other systems.
In Administration, you have the opportunity to create what are known as local users.
These users are only saved in your COYO environment and otherwise have no connection to other systems.
Advantages:
- Simple and intuitive handling by inputting into the COYO front end
- Fast and direct implementation within a few minutes – even without technical expertise
- Little effort with a low number of users and/or low fluctuation in employees
Disadvantages:
- This version is complex for first-time user import with a large number of users
- Manual workload every time employees change
Use of automatic user directories with scheduled jobs
User administration by hand is often not possible – this may be due to security requirements or large numbers of users.
COYO offers you a simple, albeit technically more challenging solution:
Via user directories, you can run automated "jobs", which at set times compare your user data with that from a central directory. AD (Active Directory) and LDAP (Lightweight Directory Access Protocol) can be chosen, whereby both use the LDAP protocol, but Active Directory offers an additional opportunity to limit to just one domain. As a further option, it’s possible to import the users via Google Workspace Admin SDK or MS Graph.
Advantages:
- Synchronization and comparison are fully automated
- There’s no need for manual corrections and errors
- The most efficient data transfer option with a large number of users
- Our experts will provide assistance with configuring the settings in the COYO Administration if necessary
Disadvantages:
- Setup and initialization involve technical effort
- Synchronization only works with a corresponding configuration of your user directory
- You are personally responsible for the correct setup and network activation and may need support from the provider of the directory
Note:
COYO only reads user directories. No entry is added in your user directory if data differs in that it exists in COYO but not in the directory.
Create users via API interface
COYO has an extensive API (Application Programming Interface).
By using this interface, users can also be created when the right "key" is presented. In our REST API documentation, we provide a comprehensive list of all possible API calls. With sufficient prior knowledge, it’s also possible to create users using a suitable tool.
The alternative: a certified COYO partner or our qualified operators. A fee is charged for this, which is based on workload. If you are interested, you can simply request the service via our Service Desk.
The alternative: a certified COYO partner or our qualified operators. A fee is charged for this, which is based on workload. If you are interested, you can simply request the service via our Service Desk.
Advantages:
- Users are created directly
- One-time higher workload
- Good preparation possible
- Easy to use afterwards
Disadvantages:
- In-depth technical knowledge or consulting budget required
- An automated import does not take place
Import users via CSV file
From version 23, users and groups can also be imported directly via CSV file in the application. This can be helpful if you have an LDAP server but don’t want to/can’t connect it to the COYO server.
This is presumably the simplest and fastest method, but is subject to some restrictions.
Advantages:
- Fast and simple import of many users and groups
- CSV file can be generated from an LDAP server
- User information can be updated by adding the file again
- No additional technical workload by configuring the firewall, LDAP server, etc.
Disadvantages:
- Not all user information can be used
- Users can’t be created with the status "inactive", which prevents a query of terms of use/general terms and conditions.
