[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"doc-en-create-user-account-plesk":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":21,"docGroup":28,"docGroupIcon":28,"link_fr":29,"bodyHtml":30},"\u002Fdocs\u002Fen\u002Fcloud\u002Fhebergement-web\u002Fcreate-user-account-plesk","create-user-account-plesk","How to Create a User in Plesk","Create an additional user account in Plesk on your Winheberg web hosting, role selection, subscription access, email activation and custom user role creation.","cloud","hebergement-web","tabler:user-plus","2026-09-20","Winheberg",92,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fcreate-user-account-plesk.webp",[16,17,18,19,20],"Plesk","Users","Roles","Permissions","Web Hosting",[22,23,24,25,26,27],"create plesk user","plesk user role","plesk permissions","plesk user account","plesk access","web hosting","","\u002Fdocs\u002Fhebergement-web\u002Fcreer-utilisateur-plesk","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>A \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fcloud\u002Fweb-hosting\">Winheberg web hosting\u003C\u002Fa> plan ships with a single Plesk login, the one belonging to the subscription owner. As soon as several people work on the same website, sharing that single login becomes uncomfortable. Everyone sees everything, and the password ends up travelling from inbox to inbox.\u003C\u002Fp>\n\u003Cp>Plesk lets you create additional user accounts. Each account is given a role that decides what the person can do once logged in, such as managing files, administering databases, creating mailboxes or simply reading statistics. A freelance developer can upload files and nothing else, without ever touching the mailboxes or the other accounts. That is the right way to let them follow our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fdeploy-nodejs-application-plesk\">How to Deploy a Node.js Application on Plesk\u003C\u002Fa> without handing over the owner login.\u003C\u002Fp>\n\u003Cp>This guide covers creating a user account in Plesk, picking the right role, and building a custom role when the predefined ones do not match how your team works.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The Winheberg Plesk panel is displayed in French. Menu, field and button names are quoted below exactly as they appear on screen, followed by their English meaning.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A Winheberg web hosting plan with access to the Plesk panel\u003C\u002Fli>\n\u003Cli>A Plesk account allowed to manage users and roles, which is the case for the subscription owner account\u003C\u002Fli>\n\u003Cli>A valid email address for the person you are granting access to\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The account created here grants access to the Plesk panel. It is neither a mailbox, nor an additional FTP account, nor a database user, each of which is created from its own section.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>1. Open the Users section\u003C\u002Fh2>\n\u003Cp>Log in to your Plesk panel, then open \u003Cstrong>Utilisateurs\u003C\u002Fstrong> (\u003Cem>Users\u003C\u002Fem>) in the side menu. You land on the \u003Cstrong>Comptes utilisateur\u003C\u002Fstrong> (\u003Cem>User Accounts\u003C\u002Fem>) tab, which lists the logins already in place on your subscription.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fcreate-user-account-plesk-1789900996315-1fcfdfe45e48a980663a76ae.webp\" alt=\"Users entry in the Plesk side menu\" width=\"400\" \u002F>\n\n\u003Ch2>2. Fill in the general information\u003C\u002Fh2>\n\u003Cp>Click \u003Cstrong>Créer un compte utilisateur\u003C\u002Fstrong> (\u003Cem>Create User Account\u003C\u002Fem>). The first part of the form, \u003Cstrong>Informations générales\u003C\u002Fstrong> (\u003Cem>General Information\u003C\u002Fem>), identifies the person and sets their scope.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fcreate-user-account-plesk-1789901468115-e07ccc574802789e14529f38.webp\" alt=\"General Information section of the Plesk user account creation form\" width=\"775\" \u002F>\n\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Fields in the General Information section\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field on screen\u003C\u002Fth>\n\u003Cth>What it expects\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Nom du contact (\u003Cem>Contact name\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The name displayed in the user list, mandatory\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Adresse mail (\u003Cem>Email address\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>An address on one of your hosted domains, which Plesk can create, or an external one\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Adresse mail externe (\u003Cem>External email address\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The backup address used to reset the password\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Rôle de l&#39;utilisateur (\u003Cem>User role\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The role that sets the permissions, covered in the next step\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Accès aux abonnements (\u003Cem>Access to subscriptions\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The subscription the person will manage, the \u003Cstrong>Tout\u003C\u002Fstrong> (\u003Cem>All\u003C\u002Fem>) value covers every one of them\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003Cdiv class=\"md-table__footer\">Only the contact name is mandatory in this first part.\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cdiv class=\"markdown-alert markdown-alert-important\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M12 22c5.523 0 10-4.477 10-10S17.523 2 12 2 2 6.477 2 12s4.477 10 10 10z\"\u002F>\u003Cpath d=\"M12 8v4\"\u002F>\u003Cpath d=\"M12 16h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The external email address must stay reachable even when the hosting is down. An address hosted on the very domain the user administers does not serve that purpose during an outage.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>3. Pick the right role\u003C\u002Fh2>\n\u003Cp>The role is what this page is really about, it decides what the person sees after logging in. Plesk ships with four ready made roles.\u003C\u002Fp>\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Roles shipped with Plesk\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Role on screen\u003C\u002Fth>\n\u003Cth>Default scope\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Propriétaire (\u003Cem>Owner\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>Every permission, including managing other users and roles. This role cannot be edited\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>WebMaster\u003C\u002Ftd>\n\u003Ctd>Every permission except managing users and roles\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Application User\u003C\u002Ftd>\n\u003Ctd>No Plesk service permission, the role is meant for access to applications only\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Comptable (\u003Cem>Accountant\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>No Plesk service permission, to be completed as needed\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003Cdiv class=\"md-table__footer\">The permission set is displayed by opening the role from the Rôle de l'utilisateur tab.\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>The \u003Cstrong>WebMaster\u003C\u002Fstrong>, \u003Cstrong>Application User\u003C\u002Fstrong> and \u003Cstrong>Comptable\u003C\u002Fstrong> roles can be edited like a custom role. If none of them fits, jump to step 5 to build one, then come back and finish creating the account.\u003C\u002Fp>\n\u003Ch2>4. Set the credentials and activate the account\u003C\u002Fh2>\n\u003Cp>The second part of the form, \u003Cstrong>Préférences de Plesk\u003C\u002Fstrong> (\u003Cem>Plesk Preferences\u003C\u002Fem>), holds the login credentials. Contrary to a common assumption, it is the \u003Cstrong>Nom d&#39;utilisateur\u003C\u002Fstrong> (\u003Cem>Username\u003C\u002Fem>) that is used to log in, not the email address.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fcreate-user-account-plesk-1789901713936-7263569be9fdf972f5d72fc8.webp\" alt=\"Plesk Preferences section of the user account creation form\" width=\"775\" \u002F>\n\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Fields in the Plesk Preferences section\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field on screen\u003C\u002Fth>\n\u003Cth>What it expects\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Nom d&#39;utilisateur (\u003Cem>Username\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The panel login name, mandatory\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Mot de passe (\u003Cem>Password\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The initial password, mandatory, with a \u003Cstrong>Générer\u003C\u002Fstrong> (\u003Cem>Generate\u003C\u002Fem>) button to produce a random one\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Confirmer le mot de passe (\u003Cem>Confirm password\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The same value, typed again\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Langue de Plesk (\u003Cem>Plesk language\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The panel display language for this person\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003Cdiv class=\"md-table__footer\">Fields marked with a red asterisk in the panel are mandatory.\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>The \u003Cstrong>Utilisateur actif\u003C\u002Fstrong> (\u003Cem>User is active\u003C\u002Fem>) checkbox is ticked by default and makes the account usable right away. Clear it when you are preparing access ahead of time and want to open it later.\u003C\u002Fp>\n\u003Cp>The \u003Cstrong>Activer le compte par mail\u003C\u002Fstrong> (\u003Cem>Activate account by email\u003C\u002Fem>) checkbox keeps the account inactive until the person confirms it from the message received on their external email address. The password still has to be set in the form, but you know the access is only used once the address has been validated.\u003C\u002Fp>\n\u003Cp>Confirm with \u003Cstrong>OK\u003C\u002Fstrong>. The account shows up in the list and the person can log in at the usual panel address.\u003C\u002Fp>\n\u003Ch2>5. Create a custom role\u003C\u002Fh2>\n\u003Cp>The predefined roles cover common cases, not necessarily yours. From \u003Cstrong>Utilisateurs\u003C\u002Fstrong>, open the \u003Cstrong>Rôle de l&#39;utilisateur\u003C\u002Fstrong> (\u003Cem>User Roles\u003C\u002Fem>) tab, then click \u003Cstrong>Créer un rôle d&#39;utilisateur\u003C\u002Fstrong> (\u003Cem>Create User Role\u003C\u002Fem>).\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fcreate-user-account-plesk-1793567751526-a31ceb9e2d94640d9c222500.webp\" alt=\"User Roles tab and Create User Role button in Plesk\" width=\"760\" \u002F>\n\n\u003Cp>Give the role a self explanatory name in \u003Cstrong>Nom du rôle de l&#39;utilisateur\u003C\u002Fstrong> (\u003Cem>User role name\u003C\u002Fem>). Every permission in the \u003Cstrong>Accès aux services de Plesk\u003C\u002Fstrong> (\u003Cem>Access to Plesk services\u003C\u002Fem>) section is set to \u003Cstrong>Refusé\u003C\u002Fstrong> (\u003Cem>Denied\u003C\u002Fem>) by default, switch to \u003Cstrong>Accordé\u003C\u002Fstrong> (\u003Cem>Granted\u003C\u002Fem>) only the ones the person needs.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fcreate-user-account-plesk-1793567752036-a37d52e3ea79ad9c62118d7a.webp\" alt=\"User role creation form with Granted or Denied permissions\" width=\"640\" \u002F>\n\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Permissions of a Plesk role\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Permission on screen\u003C\u002Fth>\n\u003Cth>What it allows\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Gérer les utilisateurs et rôles\u003C\u002Ftd>\n\u003Ctd>Create and edit other user accounts and roles, keep it for trusted people\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Créer et gérer les sites\u003C\u002Ftd>\n\u003Ctd>Add domains and change hosting settings\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Gérer les journaux\u003C\u002Ftd>\n\u003Ctd>Set the website log rotation\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Créer et gérer les tâches planifiées\u003C\u002Ftd>\n\u003Ctd>Schedule automated tasks\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Configurer le filtre anti-spam\u003C\u002Ftd>\n\u003Ctd>Set the mail spam filter\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Configurer l&#39;antivirus\u003C\u002Ftd>\n\u003Ctd>Set the mail antivirus\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Créer et gérer les bases de données\u003C\u002Ftd>\n\u003Ctd>Create databases and their users\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Configurer et exécuter les fonctions de sauvegarde et restauration des données\u003C\u002Ftd>\n\u003Ctd>Run a backup and restore data\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Afficher les statistiques\u003C\u002Ftd>\n\u003Ctd>Read consumption and traffic reports\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Concevoir des sites dans Presence Builder\u003C\u002Ftd>\n\u003Ctd>Use the Presence Builder site builder\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Envoyer et gérer les fichiers\u003C\u002Ftd>\n\u003Ctd>Use the panel file manager\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Créer et gérer les comptes FTP supplémentaires\u003C\u002Ftd>\n\u003Ctd>Open a dedicated FTP access for a contractor\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Gérer les paramètres DNS\u003C\u002Ftd>\n\u003Ctd>Edit the DNS zone of the subscription domains\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Créer et gérer les comptes mail\u003C\u002Ftd>\n\u003Ctd>Add and remove mailboxes on the domain\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Créer et gérer les listes de diffusion\u003C\u002Ftd>\n\u003Ctd>Manage the domain mailing lists\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cdiv class=\"markdown-alert markdown-alert-warning\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M10.29 3.86L1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z\"\u002F>\u003Cline x1=\"12\" y1=\"9\" x2=\"12\" y2=\"13\"\u002F>\u003Cline x1=\"12\" y1=\"17\" x2=\"12.01\" y2=\"17\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The \u003Cstrong>Gérer les utilisateurs et rôles\u003C\u002Fstrong> (\u003Cem>Manage users and roles\u003C\u002Fem>) permission lets its holder widen their own rights by creating a more permissive role. Grant it sparingly.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>A contractor in charge of connecting your domain name needs the \u003Cstrong>Gérer les paramètres DNS\u003C\u002Fstrong> (\u003Cem>Manage DNS settings\u003C\u002Fem>) permission, the full procedure is described in our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fconnect-external-domain-plesk\">How to Connect an External Domain to Your Plesk Hosting\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Confirm with \u003Cstrong>OK\u003C\u002Fstrong>. The role then appears in the \u003Cstrong>Rôle de l&#39;utilisateur\u003C\u002Fstrong> menu of the account creation form.\u003C\u002Fp>\n\u003Ch2>Troubleshooting\u003C\u002Fh2>\n\u003Ch3>❌ The account creation button is missing\u003C\u002Fh3>\n\u003Cp>This action depends on subscription permissions, not only on your panel.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check that you are logged in with the subscription owner account\u003C\u002Fli>\n\u003Cli>If you are using a secondary account, its role must grant \u003Cstrong>Gérer les utilisateurs et rôles\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Open \u003Cstrong>Compte\u003C\u002Fstrong> (\u003Cem>Account\u003C\u002Fem>), then your subscription, \u003Cstrong>Droits\u003C\u002Fstrong> (\u003Cem>Permissions\u003C\u002Fem>) tab, and check that \u003Cstrong>Gestion des comptes utilisateur supplémentaires\u003C\u002Fstrong> (\u003Cem>Management of additional user accounts\u003C\u002Fem>) reads \u003Cstrong>Activé\u003C\u002Fstrong> (\u003Cem>Enabled\u003C\u002Fem>)\u003C\u002Fli>\n\u003Cli>If in doubt, open a ticket with the \u003Cstrong>Technical\u003C\u002Fstrong> department and fill in the \u003Cstrong>Related Product\u003C\u002Fstrong> field\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The user never receives the activation email\u003C\u002Fh3>\n\u003Cp>The message is sent to the external email address, and the \u003Cstrong>Activer le compte par mail\u003C\u002Fstrong> box must have been ticked before confirming.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Reopen the user page and check the spelling of the external email address\u003C\u002Fli>\n\u003Cli>Ask the person to check their spam folder, the message looks like an automated transactional email\u003C\u002Fli>\n\u003Cli>If that address belongs to the hosted domain and the domain is not live yet, the message cannot arrive, use a third party address instead\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ Login is refused although the account exists\u003C\u002Fh3>\n\u003Cp>The expected identifier is not always the one people assume.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The field to fill in is the \u003Cstrong>Nom d&#39;utilisateur\u003C\u002Fstrong>, not the email address entered in the general information\u003C\u002Fli>\n\u003Cli>Check that the \u003Cstrong>Utilisateur actif\u003C\u002Fstrong> box is ticked on the person page\u003C\u002Fli>\n\u003Cli>If the password was generated automatically, make sure it was copied in full, with no space added on paste\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The user logs in but sees almost nothing\u003C\u002Fh3>\n\u003Cp>The account works, its role is too restrictive or its scope too narrow.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Open the role from the \u003Cstrong>Rôle de l&#39;utilisateur\u003C\u002Fstrong> tab and check which permissions are actually granted, the \u003Cstrong>Comptable\u003C\u002Fstrong> and \u003Cstrong>Application User\u003C\u002Fstrong> roles grant none by default\u003C\u002Fli>\n\u003Cli>Check the \u003Cstrong>Accès aux abonnements\u003C\u002Fstrong> field, a user limited to one subscription will not see the others\u003C\u002Fli>\n\u003Cli>Ask the person to log out and back in after their role has been changed\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Create one account per person rather than one shared team account, revoking a single access then becomes possible without disturbing anyone else\u003C\u002Fli>\n\u003Cli>Start from the most restrictive role that works, adding a missing permission is easier than discovering an accidental deletion afterwards\u003C\u002Fli>\n\u003Cli>Use the \u003Cstrong>Générer\u003C\u002Fstrong> button rather than a hand picked password, it produces a value nobody will reuse elsewhere\u003C\u002Fli>\n\u003Cli>Name custom roles after the job rather than after the person, the role will outlive the contractor\u003C\u002Fli>\n\u003Cli>Review the user list whenever an assignment ends, a forgotten access is still an open access\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If an access stays blocked or the panel does not behave as described here, open a ticket with our support from your \u003Ca href=\"https:\u002F\u002Fbilling.winheberg.com\">client area\u003C\u002Fa>, \u003Cstrong>Technical\u003C\u002Fstrong> department, filling in the \u003Cstrong>Related Product\u003C\u002Fstrong> field with the web hosting concerned. Our team will check the permissions on the subscription side.\u003C\u002Fp>\n\u003Cp>Access split the right way means a website you can share without wondering what the other person might break 🔒\u003C\u002Fp>\n",1794526350319]