Vai al contenuto
CLUP.life

Decide takeover requests as the platform

If there is no higher-level leadership, the platform decides on the administration of a club without leadership.

AdminBase (gratuito)Verificato il 30.10.2026

Questo articolo per ora è disponibile solo in tedesco e inglese; mostriamo la versione inglese.

Requisiti

  • You have a platform role with the “takeovers” right (platform moderation or municipality and association onboarding) and a second factor.

Chi può farlo?

First responsible is the leadership of the nearest higher-level organization that has leadership; if there is none, platform moderation. It may also decide any request (fallback if association leadership does not respond). There is never an automatic takeover.

Passo dopo passo

  1. Open the requests

    Open “Takeover requests”. “Responsible: Platform moderation” or “Responsible: {name}” and the member count appear.

  2. Check the evidence

    Read the evidence text (role, membership number, authorization). On approval the person becomes owner – check carefully.

  3. Decide

    Click “Hand over administration” and confirm, or “Decline” with a “Reason”. The applicant learns the decision; the reason is stored internally only.

  4. Know the consequences

    Other open requests for the same organization are declined, waiting join requests go to the new owner. After a refusal a 30-day waiting period applies.

Trovi la funzione qui: /moderation/uebernahmen

Errori comuni e soluzioni

“A refusal needs a short reason.”
Enter a reason.
“The organization now has an administration. Decline the request.”
The request is obsolete; decline it.
“Second factor required”
Platform actions always require a passkey or authenticator app.

Da sapere

  • For a takeover from pre-filling (“claim”) there is no manual review; platform moderation can only reject a claim in case of abuse. See “Dispute a takeover”.

Articoli correlati

Non hai trovato nulla? Scrivi all’assistenza

Decide takeover requests as the platform – Guida · CLUP.life