Work as a partner in the partner portal

What the partner portal is for

As a weclapp partner, you look after your customers on the platform under your own brand. Your customers decide what you may see, and their support requests can come straight to you. This gives you no rights in your customers' weclapp. For that you still need your own weclapp access from them.

wals.pro sets up your partner portal access. You receive your partner identifier, for example musterpartner. Your addresses follow from it:

https://ai.wals.pro/partner/musterpartner is your public landing page with your branding.
https://ai.wals.pro/partner/musterpartner/login is the sign-in to the partner portal.
https://ai.wals.pro/register?partner_slug=musterpartner is the registration link for new customers.

If your account also belongs to a workspace of your own, switch to the partner portal using the name at the top of the menu. See account and access for details.

Roles

Each person has exactly one role in the partner portal. wals.pro adds the people. Each person first needs their own account with a confirmed email address.

Partner administrator: sets up the portal, publishes the branding, maintains the support route, has customers register and requests customer assignments. This role does not see support cases.
Partner support: sees customer cards and the released support cases.
Customer care: sees customer cards, but no support cases.

The role alone shows no customer. A person sees customer cards and cases only once the customer has named exactly that person in their approval. A sensible start: one person as partner administrator and at least one as partner support.

Setup

Sign in at your login address, with email and password or with Google or Microsoft, depending on how your account was created. Setup shows four items:

Your access is done once you are signed in.
Your portal branding is done once a version is published.
Customer permissions are done when wals.pro has confirmed the scope and your customers have confirmed servicing, the data view with at least the customer overview and the system overview, and brand approval for the portal and support emails for the agreed branding version.
Support delivery is done when, in addition, your support addresses are confirmed by code, the mail confirmations are in place, your support route is verified and the requesting customer people are assigned.

"Pending" for items 3 and 4 is normal at the start, because they depend on steps by wals.pro and your customers. Setup is calculated from your point of view: if a customer has not named you in their approval, the item stays open for you.

Branding: draft, preview, publish

In the Branding menu:

Enter a display name and a wordmark, each up to 120 characters.
Set the primary and accent colours as six-digit hex values. The primary colour needs enough contrast with white text (at least 4.5:1), otherwise the page rejects it.
Upload your logo: PNG or WebP, at most 2 MiB and 2048 × 2048 pixels. SVG and JPG are rejected. The platform rebuilds the image as a PNG; if the result is larger than 512 KiB, it is rejected as well. A lean PNG with a transparent background works best.
Choose Save draft. The preview appears afterwards, and later at any time via Preview draft.
Choose Publish branding.

Each publication is a new version. Your landing page shows it immediately. Your customers only see your brand once their administration has confirmed the brand approval. Your customer's menu then shows your wordmark with "AI 4 weclapp", with a note below that platform and account security come from wals.pro. A custom domain, a custom mail sender and a custom MCP address are not available at present.

Set up the support route

The support configuration is in the Portal menu. You have two options:

Own weclapp helpdesk: enter a name, support and reply addresses, your weclapp address, an API key and default values for new tickets. Your customers' support requests then become tickets in your helpdesk.
Own support email: enter a name and support and reply addresses. Support requests arrive as emails.

Keep in mind:

Decide before you save for the first time. You can connect your own helpdesk yourself only while no configuration has been saved yet. wals.pro handles a later switch to a helpdesk or to another weclapp instance for you.
Allow at least one support category. Requests in categories you have not allowed do not reach you.
You confirm both addresses with a code sent by email. It is valid for 15 minutes.
Use a dedicated API key for the helpdesk. The key is stored encrypted and never shown to you again.
Agree the verification of the helpdesk route and the first test case with wals.pro.
Every save resets the support route. Verification and assignments are needed again afterwards, and no requests arrive until then. Only change the configuration after agreeing it with wals.pro.

Finally, assign each customer person who should send requests to you. wals.pro gives you the details once the customer has confirmed their approval.

Have new customers register

The Portal menu holds your portal address, the Register a customer for this partner button, your support route and the MCP address. Give your customer your registration link. The registration names you as the requested partner. wals.pro reviews and approves each registration in person.

Important: the link alone does not connect the customer to you, and you are not notified automatically. Let wals.pro know when a customer has registered through your link. After approval, the customer's consent follows (next section).

If a customer already uses the platform, enter the customer name and purpose in Setup under Request customer assignment. This does not give you access yet. wals.pro reviews the request and then creates a proposal.

Without consent from your customer's administration you see nothing. There are three separate approvals:

Servicing: you are the servicing partner. This approval comes first.
Data view (customer side: Information access): the people you named see the released information: customer overview, system overview, support overview and support details.
Brand approval (customer side: Customer branding): the customer sees your brand in the portal and in support emails. It is usually required for support requests to you.

wals.pro creates the proposal and sends your customer's administration a link. There they see the partner, systems, your named people, the information, purpose and duration, and confirm exactly this proposal. A proposal expires after 7 days, so let your customer know in advance.

Your customer can revoke any approval or end the servicing at any time under Partner permissions. This takes effect immediately. Team and permissions explains the customer's side.

Customer cards and support cases

In the Customers menu, a customer's card appears once they have released the customer overview. With the system overview you see each system's environment, connection status and last activity. Partner support also sees the Approved support cases tab: the list with the support overview, and a case's content only with support details. Only the people named when a case was sent can see it. The card never shows credentials or ERP data.

Who handles which support

First level is you: user questions, configuration, permissions, flows and everything customer-specific.
Second level is wals.pro: only faults of the platform itself, meaning it deviates from its documented behaviour.

A request comes to you when your customer asks for support in the AI assistant, explicitly chooses you as the target and confirms the preview. This requires your customer's approvals, a verified support route, an allowed category and an assignment for the requesting person. Without that choice, the request goes to wals.pro platform support. So ask your customers to address support requests to you explicitly.

If a case turns out to be a platform fault, report it to wals.pro with the customer, time, expected and actual behaviour. The portal has no dedicated button for this yet.

Frequently asked questions

My customer is registered, but I cannot see them. The card appears only with the data view. Common causes: servicing or data view is not confirmed yet, the proposal expired after 7 days, or you are not named in the approval. Contact wals.pro for a new proposal.

I can see the customer, but no support cases. You may not have the partner support role, the customer has not released the support overview, the case predates your naming, or the request went to the platform instead of to you.

Can I change my branding? Yes, publish a new version. Your customers keep their approved version until they approve the new one. For support emails, agree the switch with wals.pro first.

A colleague needs access. They need their own account with a confirmed email address. Send wals.pro the address and the role. For them to see customers, your customers must name them in their approval.

Next: glossary or troubleshooting.