The new Branch module and upfront payment model in gSignature. More control over locations, licenses, and scalable e-mail signature management
April 2, 2026
The Branch module in gSignature. One professional e-mail signature for multiple locations
The new Branch module was designed for organizations with several offices, branches, or business units that want to maintain consistent branding while automatically differentiating location-specific contact details. Instead of creating a separate template for every office, administrators can now build one e-mail signature template and control location-based data dynamically.
This means a professional e-mail signature can remain visually consistent across the company while still displaying different office addresses, phone numbers, or local details depending on the employee’s assigned Branch. For multi-location businesses, this is a significant improvement because it eliminates the need to manage multiple nearly identical versions of the same signature.
What exactly is Branch
Branch is a module that allows you to define company locations together with their own variables. These can include an office address, a branch phone number, or any other data specific to that location. Each Branch also has its own list of assigned employees.
From a system perspective, this means the variables defined at the branch level are automatically used when generating e-mail signatures for the employees assigned to that Branch. As a result, the e-mail signature generator reflects the real company structure rather than just a flat list of users.
What makes up the Branch module
The first core element is the Branch itself, which represents a physical location or organizational unit within the company. Each Branch has a unique name within the company domain, its own set of variables, and an assigned list of employees.
The second key element is Branch variables, which are the parameters later used in the signature template. Each variable has a name, which acts as the identifier used in the template, a label visible in the interface, a default value for the branch, and additional settings that determine whether it can be overwritten by the employee and whether it is required.
In practice, these variables behave like dynamic fields in an e-mail signature generator. They are available in templates in exactly the same way as standard employee data, which makes implementation smooth and intuitive.
Creating a new Branch and assigning employees automatically
When creating a new Branch, the administrator can assign employees to it right away. The system automatically removes them from their previous branches if they were already assigned elsewhere, adds them to the new Branch, and updates their membership information in their employee profiles.
This matters because the entire process is automated. There is no need to manually edit signatures, adjust profile data, or manage extra dependencies. As a result, creating an e-mail signature for a multi-location organization becomes much simpler and more predictable.
Updating a Branch without manually cleaning up data
The Branch module was also built to support changes in the company structure just as smoothly. When editing a Branch, administrators can modify its name, the set of variables, and the list of assigned employees.
The system automatically detects who was removed from the list, who was newly added, and whether any employee needs to be automatically detached from a previous Branch. All related records are updated without manual intervention. Thanks to this, the e-mail signature generator always works with up-to-date organizational data.
Deleting a Branch and changing an employee’s assignment
If a Branch is deleted, the system automatically removes all employee assignments to that Branch, but it does not delete the employee records themselves. This means no personal or organizational data is lost.
The same logic applies when an employee moves to another Branch. When a user is transferred to a different location or removed from a Branch, the system automatically removes them from the previous list, adds them to the new one, and keeps all data synchronized between Branches and the employee profile. This is an important part of maintaining consistency in larger organizations.
How Branch works together with employees
Each employee can be assigned to one Branch, and that assignment determines which Branch variables are used when generating their e-mail signature. If a specific Branch variable is marked as overridable, the employee can set their own value. In that case, the employee’s value takes priority over the default Branch value.
This is a very practical approach because it combines centralized management with flexibility on the individual user level. The company can define standard information for the whole office while still leaving room for personal exceptions where needed.
How the Branch logic works in e-mail signatures
When generating a signature, the system follows a clear logic. First, it checks whether the employee is assigned to a Branch. Then it retrieves all variables defined in that Branch. For each variable, it verifies whether the employee has set a custom value. If so, and if the variable is allowed to be overridden, the system uses the employee’s value. Otherwise, it uses the default value defined for the Branch.
Thanks to this logic, employees from the same office automatically share the same location data, and every business e-mail signature remains consistent and up to date. Just as importantly, there is no need to create multiple versions of the same template only to support different locations.
Security and access control in the Branch module
Branch was designed with security and data isolation in mind. Branches are isolated at the company domain level, and users can access only the Branches that belong to their own domain. Attempts to access Branches from other domains are blocked.
Branch management is available only to users with the appropriate permissions, namely SuperAdmin, Partner, and CompanyManager. This ensures that the organization keeps full control over who can manage locations and variables that affect e-mail signatures.
What the Branch module brings in practice
The new Branch module is another step toward full automation and scalability. It makes it possible to create one professional e-mail signature for the entire company, automatically differentiate location-specific details, reduce the number of templates, and simplify management in organizations with complex structures.
In practice, this means the e-mail signature generator in gSignature is no longer just a tool for handling individual employee data. It starts to reflect the real company structure, including offices, locations, and internal organizational relationships.
The new upfront payment model. More predictable costs and full control over licenses
The second major part of the update is the new upfront payment model. This billing method allows the organization to pay in advance for a specific number of licenses, meaning employees, for a selected monthly or yearly billing period. This gives administrators a clear view of how many accounts they are paying for and what budget they have available in the current cycle.
This is especially important for companies that want to plan expenses without surprises on the billing side. In the upfront model, the minimum number of licenses for the initial purchase is usually 10 users, which creates clear entry rules for a paid plan from the beginning.
How to start a subscription in the upfront model
Activating a paid plan happens in the payment settings. The administrator selects a plan, such as Basic or Premium, and chooses a monthly or yearly billing period. Then they fill in the company and billing contact details, specify the number of employees they want to license, and complete the payment through a secure payment gateway.
Once the transaction is successful, the plan automatically changes to paid status, and premium features become active for the purchased number of users.
Increasing the number of licenses during an active subscription
The upfront model was created to let organizations respond flexibly to team growth. If the company needs more signatures, the administrator enters a higher license count in the settings. The change takes effect immediately, and the system automatically calculates a proportional charge for the remaining part of the current billing period.
Once the difference is paid, the new licenses become available right away. This approach works particularly well for companies that are growing quickly and do not want to wait until the end of the billing period to expand the number of active users.
Decreasing the number of licenses and scheduling changes
If the organization reduces the team size or simply needs fewer licenses, the administrator can set a lower number in the panel. However, that change does not take effect immediately, because the current period has already been paid in advance. The new lower number of licenses becomes active only from the next billing period.
The panel shows information about the pending change, so the administrator has full visibility into what has been scheduled. The same logic applies to changing the billing period, for example from monthly to yearly, as well as to price updates. New conditions are scheduled and take effect only when the subscription renews.
The ability to cancel scheduled changes
If the administrator schedules a change, for example reducing the number of licenses, and later decides to reverse it, they can do so directly from the subscription panel. After canceling the change, the subscription will renew under the current conditions with no modifications. It is a simple mechanism, but a very important one for flexible team and budget management.
Subscription renewal and payment failure handling
Subscriptions in the upfront model renew automatically at the beginning of each new monthly or yearly period. The payment is charged to the saved payment card. If the payment fails, the system makes additional attempts.
If the outstanding balance is not settled, the subscription receives Past Due status and the plan is automatically downgraded to the free version. In that case, employee e-mail signatures are removed and central management features are disabled. Once the payment issue is resolved and the payment method is updated, the system automatically restores the paid plan.
This is important for administrators because it shows not only the billing logic, but also the direct consequences of unsuccessful payment for the entire signature environment.
Customer Portal and better administrative convenience
Administrators using a paid plan have access to a dedicated Customer Portal, where they can download invoices, update payment card details, and manage invoicing information. It is a practical billing center that makes day-to-day administration easier and reduces the need to contact support for simple financial actions.
Automatic organization data refresh and better variable handling
In this update, we also improved the automatic refresh of organizational data. The Organization tab now supports automatic reinstallation of employee data and signatures, improved employee visibility, and smooth installation of Branch variables for aliases as well.
This is a very important extension because it helps maintain configuration consistency across the organization without manual intervention. In practice, it means that even more complex scenarios involving aliases and Branch variables can be implemented faster and with less risk of errors.
Additional system improvements
The update also includes additional improvements that enhance the daily user experience. Gemini AI now works correctly with all new variables, which improves the effectiveness of generating and editing templates. This is especially useful where administrators are building more advanced signature layouts and want to work faster with dynamic fields.
We also optimized billing calculations so they more accurately reflect changes in license counts. On top of that, we improved the performance of rendering large lists of e-mail signature templates, which makes a real difference in larger organizations managing many projects and signature variants.
What these changes mean for companies in practice
Combining the Branch module with the upfront payment model gives organizations a very practical set of benefits. On one side, the company can better reflect its office and location structure in e-mail signatures without creating multiple parallel templates. On the other, it gains clear billing rules, more predictable costs, and full control over the number of active licenses.
This is especially important for businesses that are growing, operating across multiple locations, or wanting to scale e-mail signatures as a centrally managed part of company communication. Thanks to these changes, a professional e-mail signature becomes not only more visually consistent, but also better aligned with the real organizational and budget structure of the business.
gSignature now supports multi-location organizations and growing teams even better
The latest gSignature updates show a very clear product direction. The Branch module brings more order to how offices, locations, and contact details are managed within a single template. The upfront payment model brings more order to licenses, budgeting, and subscription renewals.
Together, they create an environment that is more predictable, more scalable, and better suited to the needs of modern organizations. For administrators, this means less manual work and more control. For the business, it means more consistent e-mail signatures, simpler management of company structure, and better cost planning.