A support entry now sits permanently in the header. Describe your question, send it, and read our answer in the same conversation — no mail thread, no ticket number to keep track of. A small badge tells you when a reply has arrived, and the page you were on is attached automatically so we can see the context. If a page ever fails to load, the error notice links straight into the same dialog with the technical details already filled in. It also stays reachable when a licence has lapsed, which is usually exactly when there is something to ask.

A profile can now name the manager who looks after it, and every manager gets a "My team" section on their dashboard listing the profiles assigned to them. A large catalogue of consultants splits into the part that is actually theirs. The assignment is organisational, not a restriction: managers keep access to every profile either way, and only an explicit assignment changes it — saving a profile never reassigns it by accident.

After the logo, the colours. The accent that carries icons, level dots and category underlines, and the darker tone behind the cover band and section headings, are now settings of your organisation. Pick them once under settings and every export follows — the standard layout and your own templates alike. A hint warns you when a chosen colour would be hard to read, and leaving them untouched keeps exactly the colours the template ships with. Like the logo, this is part of every plan.

A profile can now carry its own phone number, so a CV names the consultant it is about — their number beside their name and e-mail. If your plan includes the contact list, a profile can instead be tied to one of your contacts for good, rather than that person being picked again at every export. Retiring a contact no longer disturbs the profiles that used it: they fall back to your default. Anonymised exports keep to initials in the contact block as well.

Choosing a colour for a skill category meant a full colour wheel, one profile at a time — which is how CVs ended up with colours that clashed or printed as grey mush. The dialog now leads with ten curated colours, each one picked to stay legible as a thin underline or a small level dot on paper and to be told apart from the other nine. The free colour field is still there for anything outside the set, and a new category starts on a palette colour the profile has not used yet.

Billing is no longer its own sidebar entry; it is a tab beside your other organisation settings, so everything you administer sits in one place. Existing links and bookmarks to the old address find their way there on their own.

Text marked as an internal comment was reliably hidden in PDF exports, but a Word or Markdown export could still carry it out of the house. Comments are now removed while the document is assembled, so no export format — and no template, present or future — can pass them on.

Switching the comment mark on and then typing only marked the first character, and typing at the end of an existing comment started ordinary text again. A comment now grows as you write. It is also easier to see and to reach: marked text carries a background tint so a comment reads as one block, and the button says that the text is left out of exports and shows its keyboard shortcut.

The current app version is displayed directly in the application. After a new release, the version notice will automatically appear on your next visit.

Internal corrections that went out right after the 1.9.0 feature release. They keep exports, profiles and settings behaving consistently under load, without touching any of your data.

In some situations the details of a booked plan — included features and limits — were not resolved cleanly. Your plan is now evaluated consistently, so the features you paid for are reliably unlocked and shown in billing and settings.

You are no longer limited to the layout we ship. Create as many export templates as you need, adapt them to the look your customers expect, and mark one as the default for your organisation. Every export dialog lets you pick a different template per document, so the same profile can go to one client as a formal CV and to another as a compact one-pager.

The logo used in exported PDFs and Word files is now a setting of your organisation instead of something fixed in the template. Upload it once under settings and every export — no matter who in your team triggers it or which template they pick — goes out with the right branding.

Talyrix keeps a record of how a profile developed over time. You can see which change was made when, follow how a consultant profile grew, and understand what an export was based on months ago. The feature was rebuilt from the ground up on the new database foundation, so it stays quick to open even for profiles with a long editing history.

The application picked up the current uRemoTech look — consistent logo, colours and wording with the Talyrix website and our other products.

Catalogues grow messy — "MS Project", "MS-Project" and "Microsoft Project" all end up in the list. You can now merge duplicates into a single skill instead of deleting them one by one. Every profile that referenced one of the duplicates keeps its rating and is moved over to the surviving entry, so nothing is lost in the clean-up.

Managers can now delete users from their organisation directly in Talyrix. When a colleague leaves, their access ends the same day, without a support request and without leaving an orphaned account behind.

Categories are now resolved per profile rather than globally. A profile only shows the grouping that actually applies to it, which keeps long skill lists readable and stops unrelated categories from appearing in exports.

Several refinements to how skills are listed and edited: better grouping, calmer spacing and labels that make it obvious what you are rating.

Selecting a batch of skills and removing them in one go could previously run into itself and leave the catalogue in an inconsistent state. Bulk deletion is now processed as one protected operation with an explicit check, so what you see after the deletion is what actually happened.

Final optimisations after the move to the new database. Opening profiles, loading the dashboard and generating exports all got noticeably quicker, most visibly for organisations with many profiles and large skill catalogues.

Information about your organisation and your licence used to be fetched repeatedly while navigating. It is now loaded once and reused, which removes a noticeable delay from almost every page change.

The summary figures on the dashboard are now calculated directly in the database rather than by loading everything they summarise. The page opens quickly even when the numbers behind it are large.

Skills are read in grouped queries instead of one request per entry. Profiles with extensive skill matrices open far quicker, and the export that renders them follows suit.

Talyrix ran on two database systems in parallel during the migration. All data now lives in PostgreSQL only. That removes a whole class of synchronisation problems and is what made the speed gains of the following releases possible.

This version contains only deployment corrections for the migration. It is listed here so no version in your update history looks unaccounted for.

Profiles, skills, contacts and organisation settings were transferred to PostgreSQL. The migration ran without you having to do anything, and it is the reason profile history could return in 1.9.0 and why lists and exports have kept getting faster since.

Generating a document and opening the dashboard both got a dedicated optimisation pass. The difference is most obvious when several colleagues export at the same time.

The template settings of a new organisation used to start empty, which meant the first export could come out looking sparse. They now begin with meaningful defaults, so your very first document is presentable before you have configured anything.

If a profile referenced a user account that no longer existed, the page could fail to load entirely. Talyrix now handles the missing reference quietly and shows the rest of the information instead of an error.

The profile list could come back in a different order on every reload, so the entry you were about to click moved away. The order is now deterministic and stays the same between visits.

Export a profile with personal details removed, so you can present a consultant's experience and skills to a prospect before revealing who it is. A standard requirement in staffing and tenders, now built in rather than something you prepare by hand.

A single button exports all the profiles you have access to instead of opening each one in turn. Ideal for preparing a submission, archiving a snapshot, or handing a full team overview to a client.

Define the contact person that should appear on exported documents once. Every export uses it automatically, so a profile never goes out with the wrong person — or nobody at all — on the cover.

Skills are now written out in a cleaner structure, so an exported profile stays readable when it is pasted into a wiki, a ticket or a proposal document instead of being sent as a file.

The automatic clean-up shipped with 1.6.0 needed considerably less memory after this release, so it also completed for organisations with very large skill catalogues.

Next to PDF and Word you can now export a profile as Markdown. That makes it straightforward to move a CV into a wiki, a proposal tool or a client portal — anywhere plain, structured text works better than an attachment.

Managers can assign users to profiles and take that assignment away again. Everyone edits exactly the profile they are responsible for, which keeps larger teams out of each other's way.

Talyrix now tells you when a profile still has skills without a category or without a rating. Both quietly ruin an export — uncategorised skills end up in the wrong place, unrated ones look unfinished. You see the problem while editing instead of in the document you just sent.

Uploading a photo straight from a phone or a camera no longer causes trouble. Big images are processed reliably and scaled down for the export, keeping documents a sensible size.

Several adjustments to the exported document so sections sit better on the page and the result looks deliberate rather than generated.

Removing a skill from a category, or deleting a category outright, now leaves no remnants behind. An automatic clean-up ran once on update and removed categories that had been orphaned by earlier versions.

Updates made by a colleague could stop propagating to browser windows that were already open. The synchronisation now runs reliably in the background, so what you see stays current.

Exported CVs carry your logo instead of going out unbranded. This grew into the full tenant-level logo setting in 1.9.0.

A caching layer in front of the skill catalogue cut the loading time of profiles with extensive skill matrices.

A deleted skill category could still show up in lists and exports. It is now removed everywhere at once.

Roles created on a profile can be removed again directly, instead of staying in the list once they are no longer relevant.

Skill categories without an explicit position used to appear in an arbitrary order. They now fall into a stable, sensible place in the list and in the export.

Under certain conditions skill categories belonging to one organisation could become visible to another. The boundary between tenants is now enforced on every path that reads categories. No profile data was affected, and the fix applied to all organisations immediately on release.

Another entry that could be created but not removed got its delete button, closing a gap in the editing flow.

The test phase of the free plan now begins at a point you trigger yourself, rather than silently counting down from registration. You can set up your organisation in peace and start the evaluation period when you are actually ready to evaluate.

The number of profiles counted against your plan limit could be calculated incorrectly, which blocked the creation of a profile you were entitled to. The count is now exact.

The cancel button in the skill category dialog could be disabled, leaving no way out other than saving. It is now always available.

The user overview got a layout pass, so roles and assignments are easier to scan in larger teams.

Additional logging that lets us trace problems during profile creation faster. Nothing changes in the application itself.

Signing up with an address that already has an account now says so straight away, instead of failing later in the process with an unclear message.

Setting the languages your organisation maintains profiles in did not always take effect. The setting now saves and applies reliably.

The pricing summary describes what a plan contains more precisely, and a missing German text in the profile-limit warning was filled in.

Store the billing address of your company separately from your user account, so invoices are issued to the entity that actually pays them.

Prices now state clearly how VAT is handled, so what you see when booking matches the invoice you receive.

In a particular starting state the bookable plans were not created in full, so not every plan could be selected. Setup now completes regardless of the state it starts from.

On one route through the application the button for creating a profile was missing, leaving no way to start. It is back where you expect it.

Talyrix now reconciles subscription and payment data on a schedule. A change to your plan takes effect on time, without anyone having to nudge it.

Projects now carry a location, and the project duration appears in the exported document. Two details clients routinely ask about, and that previously had to be squeezed into the description.

Profiles, skills and contacts now greet you with a proper empty page explaining what to do first, instead of an empty list that leaves you guessing.

New organisations start in German, which matches where most of our customers are. You can switch at any time, per user and per organisation.

Navigation entries and options that your plan does not include are no longer shown. Profile assignment disappears for single-profile licences, the profiles section is hidden when you can only maintain one, and you are told clearly when the free plan applies instead of being left to work it out.

When the number of profiles your plan allows is reached, Talyrix says so up front with an explanation of what to do next, instead of refusing the action without a reason.

Account-related actions show more context about what exactly is going to happen before you confirm them.

Switching the display language could leave the skill list stale or a label empty. Available skills and categories are now reloaded on a switch, and an untranslated label falls back to a readable name instead of a blank space.

An empty project could not be saved, qualifications with unusual dates were rendered wrongly, and empty qualification blocks appeared in the export. All three are fixed, and creating a skill directly from the skill list works again.

On the Free and Pro plans skills could be missing from the exported document. Exports now contain the complete skill set your plan entitles you to.

The profile editing toolbar adapts properly to narrow windows, so editing on a laptop next to a video call is no longer a fight with the layout.

Projects can be removed from a profile directly. Outdated engagements no longer have to be emptied out field by field or left in place.

The role a consultant held in a project now appears in the exported document — often the first thing a client looks for.

Every screen now catches its own errors. If something goes wrong in one place you get a clear message and can keep working elsewhere, instead of being thrown out of the application.

Project and qualification dates could be cleared when they should not be, or refused to be cleared when they should. Both directions now work the way the form describes.

The skill input was reworked to make the most common mis-entries impossible, and empty skill categories no longer appear in the rendered template.

Organisation settings are now saved together with your company data instead of in two steps, pricing details refresh immediately after a plan change, and the payment interval is part of registration rather than something to correct afterwards.

The crop frame for profile pictures can be resized as well as moved, so you can choose the section of the photo you actually want instead of accepting a fixed cut-out. The whole image editing step got faster and more predictable along with it.

All date pickers now start the week on Monday, as expected in Europe.

Registration asks for explicit confirmation of the terms and the privacy statement, documented properly for both sides.

Sign-in now consistently uses the configured identity settings, which removes an inconsistency that could appear when logging in.

User roles were renamed from the old internal product name to the Talyrix naming scheme. Existing permissions were carried over automatically — nobody had to be reassigned.

Internal storage was renamed as part of the move from the original product name to Talyrix. No effect on your data or your work.

You pick the plan you want as part of signing up, rather than registering first and sorting out billing afterwards.

Plans and included features are published so the Talyrix website can display them directly. The prices and feature matrix you see before signing up are the same ones the application enforces afterwards.

An active free licence could be shown as inactive, which made features look locked that were in fact available.

Payment settings are loaded at runtime, so the same application works correctly against test and live payment setups.

Bookable plans, a subscription you can manage yourself, and a trial period to try Talyrix before committing. Upgrades, downgrades and cancellation are all handled in the application.

Decide which skill groups appear in an export and in which order, exclude the ones that are not relevant for a particular client, and highlight specific skills so the important ones stand out. Settings apply organisation-wide and can be overridden for a single export in the export dialog itself.

Leave inline notes in multi-language text fields — a reminder for whoever writes the other language version, without the note ever reaching the document.

The public site went live with functions, pricing and self-registration, so Talyrix could be found and tried without talking to us first.

A long list of typographic and layout work: project sections laid out more clearly, the skill matrix reordered into a more readable column arrangement, wider gaps between skill columns, primary skills sorted by level and then alphabetically, "Qualification" renamed to "Certification", and clearer labels for hourly rate and availability.

Deleting a skill or a category shows exactly what is affected before it happens, so a clean-up cannot quietly take content out of profiles you did not have in mind.

Switching the language in the rich-text editor works correctly, duplicate entries no longer appear in the skill input, unsaved changes in the skill view are flagged before you navigate away, and expired sessions are refreshed instead of causing unexplained failures.

Talyrix moved to a new frontend technology. The result is a noticeably quicker application with shorter loading times and a visible loading indicator instead of a page that appears to be doing nothing.

Change the interface language between German and English whenever you like, independently of your browser setting.

The rigid list of responsibilities was replaced by a free project description. You can describe an engagement the way it deserves rather than forcing it into bullet points.

Removing a skill or a category asks for confirmation and shows what is affected, so nothing disappears from profiles by accident.

The history of a profile was reworked to open quickly instead of making you wait for it.

Talyrix became multi-tenant. Each organisation has its own separate data, and users and managers have clearly different permissions — managers maintain the catalogue and the profiles, users work on what they are responsible for. Editing a profile is an explicit opt-in, so no one changes a document by accident.

Biography and project descriptions are written in a proper editor with formatting, and what you see while writing is what lands in the exported document.

A profile shows whether it is complete, with detailed hints about what is still missing. You know a CV is presentable before you send it, rather than finding out from the client.

The first version of the change history, recording how a profile developed over time.

Projects gained a work mode and a location, the customer field became "intermediary" to match how staffing actually works, and the end date may be left empty for ongoing engagements.

Breadcrumbs for finding your way around, toast messages confirming that an action worked, a colour picker for skill categories, a cleaner layout for multi-language fields, and delete buttons where entries could previously only be created.

Exported documents are named so you can tell them apart in a download folder, instead of arriving as a generic file name.

Entering the same skill twice is prevented, uncategorised skills export correctly, language proficiency uses proper language codes, and reloading a page no longer produces an error.

Create and maintain complete consultant profiles — personal details, projects with responsibilities, qualifications and languages — in one place instead of a folder of documents.

A structured skill catalogue with your own categories and a rating per skill, so strengths are comparable across profiles rather than described differently every time.

Turn a profile into a finished CV at the press of a button — as a PDF for sending, or as a Word document when the client wants to edit it themselves.

Upload a photo per profile and have it appear in the exported document.