Rational Synergy is licensed by user. Two kinds of licenses are discussed in this topic:
A named user license is reserved for a specific user who is specified by log in identification. Named user licenses are a good choice for users who need frequent access to Rational Synergy and must always be able to start sessions no matter how many other people are using the product. For example, it is a good idea to have named user licenses for administrators and build managers.
A floating user license enables multiple users to share the same license. For example, if two users only occasionally perform work in Rational Synergy, such as one or twice a day to synchronize their source files and complete tasks, then those users can share a floating license rather than purchasing two named user licenses. For example, a team of ten engineers may be able to share five floating licenses, depending on how frequently they need to use Rational Synergy operations. Note that a user can use a floating license only if a license is available.
Starting a Rational Synergy session does not consume a license. Only operations that update the underlying Rational Synergy database consume a license, such as file check out, task creation, or task completion. After a license is consumed by a user, that license is reserved for that user for 60 minutes after the last database update while the Rational Synergy session is running. If the user exits the session, the license is released immediately.
A single Rational Synergy installation can have a combination of named user and floating user licenses.
All features are available to all users for both named and floating licenses. There is no geographic restriction on the use of licenses.
Note that some Rational Synergy integrations hold a Rational Synergy license for the duration of time the user is running the integration. This is to ensure that source-code related operations performed through the integration can be updated in the Rational Synergy database. In this case the user can exit the visible Rational Synergy session, but the integration is still running a Rational Synergy session behind the scenes on behalf of the user.