Set up your account and integrations

My account gathers what identifies you: “Manage your sign-in details and your owner profile.” Two cards, and between them the Security card, covered separately in Turn on two-step verification.

The two cards do not serve the same purpose. User account describes the person who signs in. Owner profile describes the entity that rents, collects and invoices — and it is that entity your guests will see on their documents.

The two profile cards

1. User account: the person

   Two fields, Name and Email, and a Save button. Changing the address is not a small thing: the screen warns — “Email not verified. Changing the email will send a new verification link.” — and it is the new address that receives that link.

2. Owner profile: the entity

   Display name, Type (Individual or SCI), Legal name, Phone, then Address, Postal code, City and Country (ISO 2). The display name is the only field required in order to save.

   This block feeds your commercial documents. Filling it in early spares you from hunting for it the moment an invoice has to go out.

3. Declared capacity and your site's legal identity

   Below a new separator, You are acting as offers three choices: Professional (company, property manager, professional landlord), Individual, or Non-professional legal entity (family SCI, etc.) — this is what decides your consumer status and how long your acceptance proofs are kept. A Professional account then reveals the SIREN number field (nine digits, no spaces).

   Further down, the Legal identity block composes your booking site's Legal notice page (French law of 21 June 2004, art. 6-III): Legal form, Share capital, Legal representative, then Consumer mediator (Mediator name, Mediator website — required for a professional). A non-professional account also sees Publish my identity on my site — unchecked by default, it alone decides whether your name appears on the public page; a professional has no such choice, their identity is published regardless. A Legal notice of your site card summarizes the state of that page: complete, or the list of what is still missing before you can publish your site.

4. Guest invoice issuer

   Below a separator, the same card carries Guest invoice issuer: Company ID (SIRET), VAT number and Invoice legal notice. The screen states the exact reach — “Required for compliant invoices: this information appears on invoices issued for your direct bookings.”

   The notice field takes free text, reprinted in the invoice footer; the example the screen suggests is “VAT not applicable, art. 293 B of the French Tax Code”.

   

The API & integrations page

API & integrations is the overview of everything the account connects to. It is only visible to whoever may manage billing — a Staff member or a Read only role will not find it in their navigation. Three blocks follow one another there.

Payments collection comes first, in compact form: a status badge — To connect, Active or one of the states in between — and the Set up my payments button, which leads to the guided wizard on the Payments page. The full journey is described there; what lands on your account afterwards is covered in Track your revenue.

Connected locks comes next: “Connect your lock provider to automatically generate guest access codes at confirmation.” The step-by-step path, provider by provider, lives in Connect a lock and give guests access.

OAuth applications last, to plug in your own tools: “Connect your tools to the YStay API by creating OAuth applications (client credentials).” Create an application asks for a name and at least one scope under Scopes (permissions), and the View the API documentation → link opens the technical reference.

An application opens the whole account to the tool that uses it. Creating one is therefore reserved for the owner and for Managers who hold every right on every property. A manager limited to specific properties, or whose rights have been reduced, still sees the form, but the request is refused and the page shows the reason. When an external tool asks you to authorize its access to your YStay account, the same rights are required — all of them, on every property — whatever the role. Tools that are already authorized are cut further down, in the Connected applications card.

Each application row says who created it: “Created by Marie Dupont”, or “Unknown creator” when no creator is on record. It is more than a label: an application follows the rights of its author.

Connected applications

Under the list of your applications, the Connected applications card shows the other side of the relationship: not the applications you created, but those from other publishers — “Applications from other publishers that you or your team have authorized to access your account.” While none is connected, it reads “No third-party application has access to your account.”

Each application takes up one row:

• its name, with the Disabled by the publisher badge when the publisher has taken it out of service — the access it received from you still has to be cut on your side;
• its scopes, with the labels you see when creating an application (“Read reservations”, for example), or the raw code when a scope has no label;
• “Connected on” followed by the date of the authorization, then “Last used on” followed by the date — or “Never used”;
• “Connected by” followed by the names of the people who gave the authorization;
• the end of the access: “Access valid until” followed by the date, then the mention “then reconnection required”.

Revoke access opens a confirmation — “Revoke access for PriceTool?” — that restates the effect: “The application immediately loses access to your account and no longer receives your notifications. To reconnect it, you will need to authorize it again.” Confirming with Revoke access shows “Access for PriceTool revoked.”; if the action fails, the screen answers “Unable to revoke access.” and nothing has changed. What the action does, precisely:

• It acts immediately. The application's access to your account and its ability to renew it disappear together, as do authorizations granted but not yet exchanged. The notifications this application received from your account stop.
• It only touches your account. The application is not deleted, and the access that other accounts have granted it does not change. If you test your own public application by authorizing it on your account, it also appears in this card: revoking that access does not delete it, and does not touch its notification subscriptions.
• Reconnecting means authorizing again. There is no button to restore a revoked access: the application has to ask you for authorization again, and the same rights requirement as above applies — all of them, on every property.

The action is reserved for the owner and for Managers, like the rest of the page. Unlike creating an application or authorizing a tool, though, it does not require holding every right on every property: revoking an access gives nothing to anyone.

The YStay team can also cut an application's access, from its own console: the action requires a reason, and it is recorded, reason included, in your account's audit log. It cannot, however, do it by signing in to your account in your place: in that case Revoke access is refused to it, and only the list remains viewable.

A granted access does not last forever. The application renews its access as it uses it: with no use at all for 90 days it lapses, and even if used every day it lapses one year at most after you authorized it. The limit is shown on the row — “Access valid until” followed by the date — and it slides at each renewal, never beyond one year after the authorization. Past that point the application has to ask you to authorize it again; YStay sends no reminder before the deadline, the tool simply stops responding. From the application's side, the renewal request is then refused with “Accès expiré ou révoqué : l'hôte doit reconnecter l'application.” — in French, as the API sends it — with no further detail.

An access authorized by a team member falls with them. If they leave the team, or lose their rights over the whole account, their authorizations are cut — see Invite your team and set their roles. The account owner's are never cut.

“Consenting user not recorded” takes the place of the name when the authorization predates the moment YStay started recording who gave it. That access is cut like the others and follows the same lifetimes; however, since the person cannot be traced, it does not fall when they leave the team.

Choose the appearance on Host Ops

In the Host Ops app, "Plus" (More) › "Compte" (Account) › "Apparence" (Appearance) offers three choices: "Clair" (Light, the default), "Sombre" (Dark) and "Automatique" (Automatic). Under the control, a help line explains: "Automatique — comme le téléphone : l'app passe en clair ou en sombre avec lui." (Automatic — like the phone: the app switches to light or dark with it). The choice applies immediately, without restarting the app. Above it, the screen says "Mémorisée sur cet appareil" (Remembered on this device): it stays on this phone, is never sent to YStay, and another phone keeps its own setting. The web dashboard stays light for now.

Switch accounts on Host Ops

At the top of each tab in the Host Ops app, a pill shows the name of the account you are working for. With a single account, it only shows that name.

When you work for several accounts (your own and the ones where you were invited), touching the pill opens "Mes comptes" (My accounts): one line per account, with "Titulaire" (Owner) for your own account or the access model (for example "Concierge", "Ménage" (Housekeeping)), followed by the number of properties when your access is restricted ("· 2 logements"). A check marks the current account.

Touching another account switches to it: the app reloads and opens that account's first tab. Everything shown afterwards, and every action, belongs to that account. An account marked "Suspendu" (Suspended) or "Double authentification à configurer sur le web" (Two-step verification to set up on the web) cannot be selected. If the current account is in that state, the blocking screen offers "Changer de compte" (Switch account) when you have another account, besides "Réessayer" (Retry) and "Se déconnecter" (Sign out).

Switching needs a connection: offline, the app stays on the current account and shows "Bascule impossible sans connexion." (Switching is not possible without a connection). If an account is no longer available to you, the app shows "Ce compte n'est plus disponible." (This account is no longer available) and returns to the account YStay still grants you. On the web dashboard, the account selector arrives later.

When the page opens read-only

A member who may not manage integrations, but who was led there by a link, gets a banner instead of a form: “Managing integrations is reserved for the owner and managers. You can view existing applications.”

Locks and payments follow the same logic, each with its own wording: “Only an account administrator can connect or disconnect a provider.” and “Only an account administrator can connect payments.”

Next

• Turn on two-step verification — the Security card on this very page.
• Invite your team and set their roles — who sees what, and on which properties.
• Create your account and your first listing — the first journey, where these details appear for the first time.
• Your site: legal notice — the two templates, what the generated page contains, and what blocks publishing your site.
• Team & account — the other guides in this section.