Welcome to ADONIS!

Thank you for your interest in ADONIS. This Quick Start Guide helps you explore the key features in a Premium Test Account from an administrator perspective and take the first relevant setup checks in a structured way.

The goal is not to explain every administrative function at once. The goal is to help you understand the areas that matter first in a test account: login, users, scenarios, rights, repositories, and Process Portal basics.

Wskazówka

You don’t need to follow the steps in the exact order. Skim once, then focus on the parts you need most.

Before You Start

• You received a credentials sheet containing the login details and URL for the test account.
• The test account already includes the ADOmoney Bank sample content by default.
• Users, groups, scenarios, and basic rights are already preconfigured by BOC.
• If you received your own migration package or demo content, you can import it later.

Login

1. Open the web client URL from the credentials sheet.
2. Click Administration either from the login page or from the user menu.
3. Log in with the administrator credentials from the credentials sheet.
4. Change your password on first login and make sure to remember it.

You are now ready to start exploring the Administration Toolkit.

Get to Know the ADONIS Administration and Settings

Before changing anything, get a quick overview of the areas that matter most for test accounts.

The Key Areas to Understand First

• Users: Manage users and user groups
• Rights: Review who can see and maintain which content
• System Roles / Scenarios: Review which scenarios and functions users can access
• Repositories: Review or import repositories and migration packages
• Settings (Component Settings): Control important portal behaviour such as start model and Read & Explore defaults

These areas answer four basic admin questions:

1. Who exists? → Users
2. What can they see? → Rights
3. What can they do? → System Roles / Scenarios
4. Where do they work? → Repositories

Helpful Video to Get Started

To make it easier to get started and test, here is a tutorial video covering useful first administrative steps in ADONIS.

Prefer reading over watching? In our ADONIS Administration Help you will find all settings described in detail.

(Optional) Import Your Demo Content or Own Migration Package

Use this section only if you received your own demo package.

Go to Repositories → More options → Import repository / Import migration package → Upload → Insert into active repository → Import → Review.

After the import, select that repository in the web client.

Next: Adjust Your Users

In productive environments, ADONIS accounts are often managed through SSO technologies such as SAML or SCIM. In Premium Test Accounts, however, it is common to work with the local users that are already prepared for you.

You can find these accounts in Administration → Users or on the credentials sheet.

The most important first adjustments are simple:

1. Go to Administration → Users → select a user → Edit (⋮) → General.
2. Enter the names of your testers.
3. Make sure an email address is stored for each user because this is required for password resets.
4. Distribute the login details from the credentials sheet together with the ADONIS URL.

Difference Between Reader, User, and Admin in Tests

In a Premium Test Account, you will most likely use the User role most actively because it allows full product testing. In general, the distinction is:

• Reader: Read-only access in Read & Explore
• User: Write access and scenario access to Read & Explore, Design & Document, and usually Control & Release
• Administrator: Full access to the administration environment

Next: Validate Scenario Assignments

Your credentials sheet lists the preconfigured Administrators, Users, and Readers. Your responsible BOC contact has already created the basic setup. At this stage, your job is not to redesign it. Your job is to validate that it matches the sheet and behaves as expected.

Open Administration → System Roles & Scenarios and look at the Scenarios overview.

For a Premium Test Account, you should see the three main scenarios used for testing:

• Design & Document
• Read & Explore
• Control & Release

Now compare the configuration to the credentials sheet:

• Users should normally have access to all three scenarios
• Readers should normally have access only to Read & Explore

A good practical check is to log in once with each relevant profile:

• As a Reader, verify that Read & Explore opens and shows only released content
• As a User/Modeller, verify that Design & Document opens correctly
• As a user involved in release, verify that Control & Release is available

If anything is inconsistent, do not rebuild the test configuration yourself. Contact your BOC Account Manager or the Hotline with:

• The affected account name
• The expected scenario(s) from the credentials sheet
• Ideally a screenshot of the Scenarios overview

Next: Get Familiar with Rights and Visibility

Once scenarios are confirmed, the next question is not only which screens users can open, but also what they can actually see and maintain there.

Open Administration → Rights to review what each audience sees and can do. Switch between Users and Readers from the credentials sheet and use the built-in sample content as your reference.

Use ADOmoney Bank as Your Concrete Example

In the Rights view, expand the repository tree to:

01 Processes → 02 Core Processes → CP 0.1 Advise Customer

Then validate the following:

• For Readers, this area should be read-only so released processes are visible in Read & Explore.
• For Users/Modellers, confirm that they have edit rights where they are expected to work.

Rights usually inherit down the tree. That means a read grant on 02 Core Processes will typically flow to CP 0.1 Advise Customer and its submodels unless you override it.

What Else to Check While you are Here

• Object rights: Users should be able to see referenced objects such as Roles, Org Units, Documents, and Applications where required
• Component rights: Readers should get Read & Explore, Modellers should get Design & Document, and users involved in approvals should get Control & Release
• Language rights: Confirm that the visible language setup matches the intended testing setup

A useful round-trip check is:

• Sign in as a Reader and open Read & Explore
• Navigate to CP 0.1 Advise Customer and confirm visibility
• Sign in as a User/Modeller and verify that editing works only where intended

If something is wrong, adjust the right at the folder or model level where possible instead of granting broad access too high in the structure.

Wskazówka

Once you are more familiar with the tool, you can explore advanced options such as Language rights and Metamodel rights. These are useful for regional rollouts or simplified beginner setups, but they are not the first priority in a Premium Test Account.

Next: Configure the Process Portal

Go to Settings → Read & Explore → General. This page controls the portal experience for the largest audience in your company: Readers.

In a Premium Test Account, the most important principle is simple: leave the governance-relevant defaults as they are unless you have a good reason to change them.

That is especially relevant for settings that influence what Readers can see, for example whether only released content is shown.

One Safe and Useful Change

A practical change you can make is the Start Model per repository.

By default, the Process Landscape of the ADOmoney Bank sample content is set. Once you create or import your own Process Landscape, you can set that model as the entry point so Readers land there first.

This improves orientation without weakening governance.

Wskazówka

You might want to import your own BPM assets or models at this stage. These imports are not performed in the Admin Toolkit. Excel imports for assets such as Roles, Org Units, or Applications and BPMN DI imports for process models are carried out in the Design & Document scenario. For this Admin guide, it is enough to verify that the necessary scenarios and rights are in place.

Essentials Accomplished

At this point, you have completed the most important first checks for a Premium Test Account:

• Administrator login works
• The correct repository is active
• ADOmoney is available as a reference
• Users and emails are adjusted where needed
• Scenario assignments match the credentials sheet
• Rights reflect read versus edit access
• Read & Explore is configured with safe defaults

Final Checklist

Use this short checklist before handing the environment over to colleagues for testing:

• Admin login works and the correct repository is active.
• ADOmoney is visible by default.
• The scenario assignments match the credentials sheet.
• Rights correctly reflect read vs. edit behaviour in ADOmoney.
• Read & Explore → General is left at its safe defaults except for an optional repository start model.
• A release test confirms that a process becomes visible to Readers once it is Released.

Great job. You have successfully completed the first relevant administrator steps in ADONIS and can now continue testing the software with your colleagues.

Continue Learning with Self-Service Resources

Congratulations, you made it to the end of this ADONIS Quick Start Guide for productive administrators. You have completed the first steps to start working in a structured way in your productive ADONIS environment.

To keep building confidence and solve questions independently, use the following self-service resources:

When you Need Practical Product Help

Use the BOC Support Center and the ADONIS Online Help when you need step-by-step guidance for concrete tasks such as user management, permissions, repositories, settings, authentication, or troubleshooting.

When you Want to Learn Visually

Use the ADONIS tutorial videos if you prefer to see workflows in action rather than read through longer documentation.

When you Want to Understand the Administration Area Better

Use the Administration Help pages as your main reference for all detailed administrative capabilities and configuration options.

Suggested Self-Service Learning Path

A practical next-step sequence is:

1. Use this Quick Start Guide for your first productive admin tasks.
2. Use the ADONIS Administration Help whenever you get blocked in a specific activity.
3. Use the BOC Support Center when you need additional product help or FAQs.
4. Use the tutorial videos when you want to see the workflow visually.
5. Deepen your understanding of your productive setup step by step as new admin tasks come up.

Wskazówka

For any further questions or concerns, reach out to your BOC contact person.