Changing name of a passenger after ticketing is not a quite regular amendment case - so in GO7 it does not go by the same rules and policies as a regular amendment, and offers much more flexibility.
There are two cases in setting those policies up: direct customer setup and agent setup. Let's see both of them:
Direct Customer case
In case of direct customers, GO7 administrator has two options to control the name change flow: the TKT PAX change permission on the user-level, and the Name change fee on the class level.
Name change fee will be charged per changed PAX per service. For example, if there are 2 services in a PNR, from two different classes - one with 10$ fee, and another with 20$ fee, and one want to change 3 PAX names - total fee of 90$ ((10$+20$)*3pax) will be charged.
Although, users with TKT PAX change permission will be able to change PAX names for free. Users without this permission will pay the fee if set, and won't be able to change names at all if the fee is not set.
Agents will also be affected with the name change fee the same way as users are. But in this case, you have an additional class-level option - Allow free name change for agents. If this option checked, agents will be able to change names for this services for free, disregarding user permissions and the name change fee for this class.