Add a client
Register a new company in a few clicks, with validated details.
Answers about your Nango workspace: how teams work inside the app, what each area is for, and how billing and security fit together.
If you don’t see your case here, use the Contact page on this site or write us from your workspace — we’ll point you to the right place.
Short in-app demos — from adding a client to approvals and AI-assisted contract review.
Register a new company in a few clicks, with validated details.
Move from offer to contract without Word files and lost emails.
Keep annexes linked to the contract with the same history.
Get an indicative summary before legal review.
Define who approves and track requests in the inbox.
A workspace is your company’s isolated environment in Nango: your clients, offers, contracts, users, and settings live together and are secured. Each workspace has its own dedicated company subdomain.
Use the signup form and follow the validation steps; you will receive access to your company URL and can invite colleagues. The exact steps may vary if your organisation uses a custom onboarding process.
Workspaces are typically accessed via the hostname assigned at signup (for example a subdomain). If you need a custom domain or other deployment constraints, contact sales — enterprise-style setups are handled case by case.
Application data is stored in a secure environment within the European Union, in line with applicable legal requirements and confidentiality standards.
People in your organisation sign in to your tenant URL. Administrators can invite users, assign roles, and remove access when someone leaves. At least one user must keep permission to manage users so you are never locked out without a recovery path.
Roles bundle permissions: who can manage clients, offers, contracts, annexes, billing-related screens, API keys, and user administration. This keeps day-to-day work scoped — not everyone needs full access to settings or financial flows.
Yes. In security settings you can enable two-factor authentication and register passkeys (WebAuthn) for passwordless sign-in where supported by the browser and your devices.
The application includes audit logging so you can review important actions in context — useful for internal control and when you need to show who changed what.
Clients are your business partners: companies you quote and contract with. You maintain contacts, identifiers, and history in one place instead of scattered spreadsheets.
Where the feature is enabled, you can validate or pre-fill company data using the VAT identification number and the EU VIES service (and national lookups where configured). This reduces typos and speeds up onboarding of new clients.
Yes. You can add several contacts per client and mark who is primary so offers and communications stay aligned with the right people.
You create offers inside the workspace, track status, and share them with the client through a secure link. The counterparty can open the offer without creating an account: they can negotiate, accept, or decline within the steps you configure. Discussion and decisions stay in a transparent, time-ordered trail in the app — so you are not reconstructing what happened from scattered emails.
You can move forward to contracts and related documents in the same system, keeping continuity from commercial terms to the legal frame.
Accepted commercial terms feed into contracts and annexes in the same workspace, with structured revision rounds when terms change. You can attach files, track versions, and — where the product supports it for a record — download PDFs for internal archiving, so you keep a coherent digital file from the first offer through each amendment.
When terms need to change, you can run a structured revision: secure links for stakeholders, tracking of proposed changes, accept/reject steps, and finalisation — so negotiations stay traceable.
Series help you assign consistent reference numbers to contracts according to your internal rules, so documents stay identifiable in reporting and archives.
The native Nango Sign path is advanced electronic signature (AES) under eIDAS Art. 26. Qualified electronic signature (QES) is available on eligible plans (typically Enterprise or on request): it is not issued by Nango, but by a qualified trust service provider (QTSP) embedded in the same portal. Nango orchestrates sending, credits, and evidence.
No. Nango is not a QTSP and does not issue qualified certificates. For QES, identification and the certificate are with the QTSP partner. For AES, verification uses email OTP and, when enabled, SMS OTP in the Nango Sign portal.
Law no. 214/2024 is Romania’s framework for electronic documents and trust services, aligned with eIDAS. QES generally has the legal effect of a handwritten signature. AES remains suitable for many private B2B contracts. Which form a given instrument requires is for your organisation and counsel to decide — Nango does not certify eligibility per document, and this answer is not legal advice.
The signing module (AES) is included on plans that enable it. QES appears in the app only if the plan includes qualified signature and the platform has turned the feature on. If you do not see the QES option, you are on AES or should contact sales.
On eligible subscription plans, Nango can analyse contract or annex text and surface summaries, attention points, and indicative references to help your team prepare for legal review. It is an assistive workflow feature—not a substitute for qualified legal counsel.
Availability depends on your workspace plan and platform settings. Check the pricing page or billing area in the app, or contact sales if you need a plan that includes AI review and monthly limits.
When you run a review, relevant document text is sent to a European AI provider (Mistral) under contractual safeguards aligned with GDPR expectations for business SaaS. Outputs are stored in your workspace for traceability.
No. AI suggestions are orientative only: they do not constitute legal advice and have no legal effect. Your organisation remains responsible for all contractual decisions. See our terms of service for the full disclaimer.
You get views and exports oriented around offers and contracts (and related activity), so management can see volume and status without manual consolidation. Exact layouts depend on your plan — some advanced reporting may be limited to higher tiers.
Exports from reporting screens are intended for operational and management use. For heavy automation, the API (on eligible plans) may be more appropriate than one-off CSV copy-paste.
Subscription and invoices are tied to your workspace’s plan. You can start checkout from the billing area, open the customer portal when available, and download invoice PDFs. Plan limits (for example offers or contracts per month, annex volume, advanced reports, API) match what administrators configure centrally — the marketing site reflects the same configuration.
Where enabled, you can initiate flows compatible with bank transfer alongside card payments. Availability depends on how your subscription is set up.
The product enforces limits according to your subscription — you may need to upgrade, wait for the next period, or adjust usage. Administrators see relevant messaging in the billing or usage context.
Only users whose role includes the right permissions can open billing and payment flows, so not every team member sees financial details.
Yes, for workspaces on plans that include API access. Tenant administrators can manage OAuth clients from API settings and integrate external systems within documented limits and throttling.
API features are gated by subscription. If your plan does not include API access, the settings entry will not appear or will indicate that an upgrade is required.
Access requires authentication; sensitive actions can be further protected with 2FA or passkeys. Secure data separation between platform users helps prevent data mixing at application level.
Yes — a help section is available in the workspace with articles for common tasks. For anything specific to your contract or rollout, support or sales is available to assist.
Use your usual support channel (email or in-product contact, depending on contract terms). Critical security issues should be reported through the process described in your security or abuse documentation.