The Permissions profile is used to define Permissions settings (who can see and/or do what) by module (AR, FR, PM, etc…) and Table. The profile also defines Button permissions and Access Rights for various functions in RecTrac.
See Also: Topic Doc - RecTrac Permissions.
Making changes to a profile is an Audited Event. Additionally, Linking, Removing, Purging, and Cloning profiles are also Audited Events.
See Also: Topic Doc - RecTrac Profile Assignments Screen, Hierarchy Guide, and Profile Listing.
Core Information
Activity Enrollments - Allow Override (SAProfileDetails_ARAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Activities. Users can also bypass Maximum Enrollment Counts on Activities.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Activity Enrollment - Override Codes (SAProfileDetails_AROverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteActivity Visit - Allow Override (SAProfileDetails_ARVAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Activities Visits.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Activity Visit - Override Codes (SAProfileDetails_ARVOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeletePass Memberships - Allow Override (SAProfileDetails_PMAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Pass Memberships.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Pass Memberships - Override Codes (SAProfileDetails_PMOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeletePass Visits - Allow Override (SAProfileDetails_PMVAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Pass Visits.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Pass Visits - Override Codes (SAProfileDetails_PMVOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteFacility Reservation - Allow Override (SAProfileDetails_FRAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Facility Reservations.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Facility Reservation - Override Codes (SAProfileDetails_FROverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteRental Reservations - Allow Override (SAProfileDetails_RNAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Rentals.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Delete
Rental Reservations - Override Codes (SAProfileDetails_RNOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteLocker Reservations - Allow Override (SAProfileDetails_LKAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Lockers/Locker Rooms. Users with this Permission can also view and print Lock Combinations.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Delete
Locker Reservations - Override Codes (SAProfileDetails_LKOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteTrip Registrations - Allow Override (SAProfileDetails_TPAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Trip bookings.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Trip Registrations - Override Codes (SAProfileDetails_TPOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteCourt Reservations - Allow Override (SAProfileDetails_CRAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Court bookings.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Delete
Court Reservations - Override Codes (SAProfileDetails_CROverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeletePersonal Trainer - Allow Override (SAProfileDetails_PTAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Personal Trainer bookings.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Personal Trainer - Override Codes (SAProfileDetails_PTOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteLeague Registrations - Allow Override (SAProfileDetails_LSAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Leagues. Users with this Permission can also bypass League scheduling conflicts.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
League Registrations - Override Codes (SAProfileDetails_LSOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteGolf Tee Times - Allow Override (SAProfileDetails_GRAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to Tee Time bookings.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Golf Tee Times - Override Codes (SAProfileDetails_GROverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteService Items - Allow Override (SAProfileDetails_PSSAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to POS Service Items.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Service Items - Override Codes (SAProfileDetails_PSSOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteInventory Items - Allow Override (SAProfileDetails_PSIAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to POS Inventory Items.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Inventory Items - Override Codes (SAProfileDetails_PSIOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteTicket Sales - Allow Override (SAProfileDetails_PSTAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to POS Tickets.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Ticket Sales - Override Codes (SAProfileDetails_PSTOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteLeague Visits - Allow Override (SAProfileDetails_LSVAllowOverride)
Users with this Permission can bypass restrictions on Fees and Rules that are linked to League Visits.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
League Visits - Override Codes (SAProfileDetails_LSVOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteTouch Layer - Allow Override (SAProfileDetails_TouchAllowOverride)
Users with this Permission can bypass access/use restrictions for Touch Buttons by Touch Layer. Permissions can be set by Touch Button Layer. A user with matching permissions for a Layer will have access all the buttons on it. Users without Permissions to that Layer will not be able to access the buttons on it.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this module.
-
Yes - With Matching Codes- Users linked to this Permissions profile can override restrictions for this module provided:
- A match is found between the code/codes in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Matching Codes.
- Any code is found in the accompanying <Module> - Override Codes field when/if the Override Option on the restriction in question, such as a Fee or a Rule or etc., is set to Override with Rights.
- No - Users linked to the Permissions profile cannot override restrictions for this module.
Touch Layer - Override Codes (SAProfileDetails_TouchOverrideCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you want to link to this field. Depending on the Override Option on the restriction (a fee, a rule, an enrollment max count, etc.), at least one (1) match must be found or any code will suffice.
-
At Least One Exact Match Needed - When/if the Override Option on the restriction is set to Override with Matching Codes, at least one (1) of the Override Codes entered in this field must match the Override Code(s) linked to the restriction. One match only is needed.
For example, you have the following Override Codes in your database: MANAGER and CLERK. You have an "Ages 18 and Up" rule set to Override with Matching Codes and with Override Code MANAGER linked to it. Your Manager's Permission profile has the MANAGER Override Code linked in this field. Your Clerk's Permissions profile has the CLERK Override Code linked in this field. A Clerk processing a transaction for a 17 year-old patron wouldn't be allowed to override/bypass the 'Ages 18 and Up' Rule because the CLERK Override Code doesn't match either of the Override Codes linked to the Rule. However, a Manager could bypass the rule because the MANAGER Override Code linked here is a match for the MANAGER Override Code linked to the 'Ages 18 and Up' Rule. - Any Code Needed - When/if the Override Option on the restriction is set to Override with Rights, any code entered in this field will satisfy the criteria. Using the example above, both the Manager and the Clerk could complete the enrollment because they both have a code and any code will satisfy the requirement. However, if you had a user without a code in this field, that user wouldn't be able to process the enrollment.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteInventory Posting Options (SAProfileDetails_InventoryPostingOptions)
Expand the Combo Box icon to select the Inventory Posting Options you wish to allow for User IDs linked to this profile.
OR
Leave the Combo Box blank (do not select any options) to give users linked to this profile access to all Inventory Posting Options.
The selections you make here determine the entries which populate the Posting Option Drop-down lists (Inventory and Warehouse tabs) in Inventory Posting. Your options are:
- Physical Count
- Post Orders
- Post Receivings - Individual Item
- Post Receivings - Invoice Balance
- Post Receivings - PO Match
- Post Reduction
- Post Transfers
Activity Default Record Permission (SAProfileDetails_ARActivityDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Activity Section Default Record Permission (SAProfileDetails_ARSectionDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Facility Default Record Permission (SAProfileDetails_FRFacilityDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Golf Course Default Record Permission (SAProfileDetails_GRCOURSEDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Locker Room Default Record Permission (SAProfileDetails_LKLockerRoomDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Locker Default Record Permission (SAProfileDetails_LKLockerDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
League Default Record Permission (SAProfileDetails_LSLEAGUEDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Pass Default Record Permission (SAProfileDetails_PMPassDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Inventory Default Record Permission (SAProfileDetails_PSInventoryDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Service Item Default Record Permission (SAProfileDetails_PSSERVICEITEMDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Ticket Default Record Permission (SAProfileDetails_PSTICKETMAINDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Rental Default Record Permission (SAProfileDetails_RNRENTALITEMDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Delete
Trip Default Record Permission (SAProfileDetails_TPTripDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Fee Default Record Permission (SAProfileDetails_SAFeeDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Delete
Rule Default Record Permission (SAProfileDetails_SARuleDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Contract Default Record Permission (SAProfileDetails_SAContractDefaultAddRecord)
Select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
- None - The user has no options for Adding Records. Users with this permission will be allowed to add a new 'regular' File Management record only (provided NO Default Records exist for this module).
Note: When 'None' is selected, users will not have access to Default Records on any DataGrid. All Default records will be hidden, and 'Default' will not be a Status option.
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Additional Information
- "Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings, Additional Settings, etc...) and tabs (Core, Fees*, Rules*, Questions, Comments, etc…) will be copied from the Default record.
- "Default" status records to do not show up in Daily Processing DataGrids. You cannot register for, reserve, or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive, it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
- Separate Default Records for Fees and Rules can be created as well, in their respective File Management program. Permissions must be set to add a Default Record and once added, the default record can be linked as needed to any module.
Note: If you are using a Rules and Fees profile then the settings on that profile will impact whether Default Rules/Fees will be available when adding new records.
Allow User to Manage Datagrid Templates for 'Everyone'? (SAProfileDetails_AllowEveryoneForDatagrid)
Select this option to allow the User logged in to create and manage DataGrid Templates for everyone.
Disable this option to allow creation and management of DataGrid Templates for the user who is logged in only.
See Also: RecTrac DataGrids.
DeleteHide Options" Menu for all Datagrids? (SAProfileDetails_DatagridHideOptionMenu)"
Select this option to remove the Options Drop-down menu from all DataGrids for users linked to this Permissions profile. This is a universal setting in RecTrac, so when enabled, the Options menu will NOT appear on any DataGrid for users linked to this profile. Leave this option disabled to allow users linked to this profile to have access to the Options Drop-down menu on DataGrids in RecTrac.
Note: To hide the Options Drop-down list on a DataGrid by DataGrid basis, you can create Custom DataGrids and set the field within Advanced Parameters. Go to Management Screen Management and find the screen you wish to customize (For Example: ARActivityMain). Find/Select the DataGrid within the tree (For Example: ARActivityMain_DataGrid). Click Advanced Parameters. Find the option for DataGridHideOptionMenu and enable as needed.
See Also: Topic Doc - DataGrids and Topic Doc - Screen Customization.
DeleteHide Show Settings" in Options Menu for all Datagrids? (SAProfileDetails_DatagridHideOptionSettings)"
Select this option to remove the Show Settings Menu from within the Options Drop-down list for all DataGrids for users linked to this Permissions profile. This is a universal setting in RecTrac, so when enabled, the Show Settings menu will NOT appear on any DataGrid for users linked to this profile. Leave this option disabled to allow users linked to this profile to have access to the Show Settings Drop-down menu on DataGrids in RecTrac.
If the Hide "Options" Menu for all DataGrids option is enabled for this profile, then the Hide "Show Settings" in Options Menu for all DataGrids becomes superfluous and you do not need to set it. Users who cannot access the Options Drop-down from a DataGrid cannot access any menu items within it.
Note: To hide the Show Settings Menu from within the Options Drop-down list on a DataGrid by DataGrid basis, you can create Custom DataGrids and set the field within Advanced Parameters. Go to Management Screen Management and find the screen you wish to customize (For Example: ARActivityMain). Find/Select the DataGrid within the tree (For Example: ARActivityMain_DataGrid). Click Advanced Parameters. Find the option for DataGridHideOptionSettings and enable as needed.
See Also: Topic Doc - DataGrids and Topic Doc - Screen Customization.
DeleteTable Permissions
Table Permissions (SAProfile_permissions_permissions_help_SAPermissionDataDataGrid)
The Table Permissions DataGrid allows you to set Maintenance View Add Change and Delete Permissions and Inquiry View you can:
- Use InLine Editing OR
- Highlight/Select an individual record and click Change. You will continue to the Permission Data Update screen OR
- Use the fields and button at the bottom of the DataGrid to set Permissions in bulk by Function Type.
DataGrid column sort options allow you to customize the view as desired. Click here for a full description of RecTrac DataGrids.
Function Types
Function Types are as follows:
- Maintenance View - Refers to records that display on File Management DataGrids such as Activity Management Pass Management User Management System Code Management etc….
- Maintenance Add - Refers to Add buttons on File Management DataGrids.
- Maintenance Change - Refers to Change buttons on File Management DataGrids. Also refers to InLine Editing on DataGrids.
- Maintenance Delete - Refers to Delete buttons on File Management DataGrids.
- Processing View - Refers to records that display on Daily Processing DataGrids such as Global Sales and Pass Visit Processing etc….
- Inquiry View - Refers to records that display on Module Inquiry DataGrids such as Activity Inquiry Pass Inquiry etc….
- Report View - Refers to records that display on Report DataGrids such as Activity reports Pass reports System Reports etc….
Data Tables
By default Data Tables are listed alphabetically by Function Type by RecTrac module where:
|
|
|
Access Rights
Expand the Drop-down list to select your Access Right option.
- Administrator - Administrator rights. Users linked to this profile will have rights to all records in the Table for the Function selected. Permission Codes are not considered for a DataGrid/Table set to Administrator.
- With Matching Codes - Users linked to this profile will have rights to all records in the Table for the Function selected provided it has a Permission Code that matches the Code(s) you select in the Permissions Codes field. Multiple selection is allowed.
- Using Data Access Profile - Users linked to this profile will have their Table Permissions set by the Data Access profile to which they are linked. Data Access profiles are used in conjunction with Site Management and should be linked at the Site level of Profile Hierarchy.
- None - No Permissions. Users linked to this profile will have NO rights to records to the Table for the Function selected regardless of the Permissions Code(s) linked to items in the table.
Permissions Codes
This field is applicable only if your %%/SAProfile_Access Rights selection is With Matching Codes.
Expand the Drop-down list to select the Permission Code(s) you wish to link to the Tables you select. Multiple selection is allowed.
Permissions Codes are maintained in Permissions Code Management
When Permissions Code(s) are selected here Users linked to this profile will see/have access to only those records in the selected Table that have a matching code in its Permissions field. One match only is needed.
DeleteAccess Rights (SAProfileScreenOnly_BulkAccessRights)
Expand the Drop-down list to select your Access Right option. You will use this field in conjunction with the Function Types field, Permissions Codes field (if applicable) and Change All Table Permissions button to set Table Permissions in bulk to the Access Right you select.
-
Administrator - Administrator rights. Users linked to this profile will have rights to all records in all Tables set to this Access Right. Permission Codes are not considered for a Table set to Administrator.
For Example: All Maintenace View Tables are set to 'Administrator' (i.e. File Maintenance View, Inquiry View, Processing View and Report View). In this event, a User linked to this profile would see ALL Activities, ALL Facilities, ALL Rentals, All Passes, etc… in their DataGrids throughout RecTrac. -
With Matching Codes - Users linked to this profile will have rights to all records in all Tables that have a Permission Code that matches the Code(s) you select in the Permissions Codes field. Multiple selection is allowed.
For Example: All Maintenace View Tables are set to 'With Matching Codes' (i.e. File Maintenance View, Inquiry View, Processing View and Report View) and you have POOL in the Permissions Code field. In this event, a User linked to this profile would see ONLY THOSE Activities, Facilities, Rentals, Passes, etc… that have 'POOL' as their Permission Code. Activities, Facilities, Passes, Rentals, etc… set to a Permission Code other than POOL would not be visible to a User linked to this profile. -
Using Data Access Profile - Users linked to this profile will get their Table Permissions from the Data Access profile to which they are linked. Data Access profiles are used in conjunction with Site Management and should be linked at the Site level of Profile Hierarchy.
Note: This option is applicable to the Permissions profile only.
-
None - No Permissions. Users linked to this profile will have NO rights to records in Tables regardless of the Permissions Code(s) linked to items in the table.
For Example: All Maintenace View Tables are set to 'None' (i.e. File Maintenance View Inquiry View Processing View and Report View). In this event a User linked to this profile would not see ANY Activities Facilities Rentals Passes etc… in their DataGrids throughout RecTrac.
When you have made your selection click Change All Table Permissions to set the records in the DataGrid that match your Function Type to the selected Permission.
DeletePermissions Codes (SAProfileScreenOnly_BulkDataAccessCodes)
This field is applicable only if your Access Rights selection is With Matching Codes.
Expand the Drop-down list to select the Permission Code(s) you wish to link to the Tables you select. You will use this field in conjunction with the Function Types field and Change All Table Permissions button to set Table Permissions in bulk to the Code(s) you select. Multiple selection is allowed.
Permissions Codes are maintained in Permissions Code Management
When Permissions Code(s) are selected here Users linked to this profile will see/have access to only those records in DataGrids that have a matching code in its Permissions field. One match only is needed.
For Example: All Maintenace View Tables are set to 'With Matching Codes' (i.e. File Maintenance View Inquiry View Processing View and Report View) and you have POOL in the Permissions Code field on this profile. In this event a User linked to this profile would see ONLY THOSE Activities Facilities Rentals Passes etc… that have 'POOL' as their Permission Code. Activities Facilities Passes Rentals etc… set to a Permission Code other than POOL would not be visible to a User linked to this profile.
DeleteFunction Types (SAProfileScreenOnly_BulkAccessTypes)
Expand the Combo box icon to select the Function Type(s) to which you wish to link the selected Access Rights. You will use this field in conjunction with the Access Rights field, Permissions Codes field (if applicable) and Change All Table Permissions button to set Table Permissions.
Upon clicking the Change All Table Permissions button, the Access Right you select will be linked to the Function Type(s) you select here. The DataGrid will update automatically.
- Maintenance View - Refers to records that display on File Management DataGrids, such as Activity Management, Pass Management, etc…
- Maintenance Add - Refers to Add buttons on File Management DataGrids.
- Maintenance Change - Refers to Change buttons on File Management DataGrids. Also refers to InLine Editing on DataGrids.
- Maintenance Delete - Refers to Delete buttons on File Management DataGrids.
- Processing View - Refers to records that display on Processing DataGrids, such as Global Sales and Pass Visit Processing, etc….
- Inquiry View - Refers to records that display on Inquiry DataGrids, such as Activity Inquiry, Pass Inquiry, etc…
- Report View - Refers to records that display on Report DataGrids, such as Activity reports, Pass reports, etc…
When you have made your selection, click Change All Table Permissions to set the records in the DataGrid that match your Function Type to the selected Permission.
DeleteButton/Misc Permissions
Button/Field Permissions (SAProfile_permissions_permissions_help_SAPermissionDataButtonsDataGrid)
The Button/Misc Permissions DataGrid allows you to set Permissions on buttons that appear on various DataGrids in RecTrac. Generally speaking, the DataGrids in question are the File Management DataGrids for the main RecTrac modules (Activity, Pass, Rental, etc…) and Household Management/Global Sales Lookup screens. The Button Names should be self-explanitory. To update/assign Permissions on this screen, you can:
- Use InLine Editing.
- Highlight/Select an individual record and click Change. You will continue to the Permission Data Update screen.
- Use the fields and button at the bottom of the DataGrid to set Override Permissions in bulk for all records in this DataGrid.
DataGrid column sort options allow you to customize the view as desired. Click here for a full description of RecTrac DataGrids.
Button/Field Types
By default Buttons are listed alphabetically by RecTrac module where:
|
|
|
For Example: ARActivityMain_ButtonARPurge is the Activity Purge button on the main Activity Management DataGrid.
Access Rights
Expand the Drop-down list to select your Access Rights option.
- Administrator - Administrator rights. Users linked to this profile will have rights to the Button selected (i.e. the Button will be "active"). Override Codes are not considered for a Button set to Administrator.
- With Matching Codes - Users linked to this profile will have rights to the Button selected provided the User has an Override Code on his/her User ID record that matches the Code(s) you select in the Override Codes field here. One match only is needed and multiple selection is allowed.
- None - No Override Permissions. Users linked to this profile will have NO rights to the Button selected (i.e. the Button will be "grayed-out") regardless of the Override Code(s) linked on the User's User ID record or in the Override Codes field here.
Override Codes
This field is applicable only if your Access Rights selection is With Matching Codes.
Expand the Drop-down list to select the Override Code(s) you wish to link to Buttons you select. Multiple selection is allowed.
Override Codes are maintained in System Code Management. Type = Override Code.
To have access to a Button in this DataGrid that has Override Code(s) linked a User must have a matching Override Code linked to his/her User ID record. One match only is needed and multiple selection is allowed.
DeleteAccess Rights (SAProfileScreenOnly_BulkButtonAccessRights)
Expand the Drop-down list to select your Access Rights option. You will use this field in conjunction with the Override Codes field (if applicable) and Change All Button/Field Permissions button to set Button/Misc Permissions in bulk for all records in the DataGrid above.
- Administrator - Administrator rights. Users linked to this profile will have rights to the Button selected (i.e. the Button will be active"). Override Codes are not considered for a Button set to Administrator.
- With Matching Codes - Users linked to this profile will have rights Button selected provided the User has an Override Code on his/her User ID record that matches the Code(s) you select in the Override Codes field here. One match only is needed and multiple selection is allowed.
- None - No Override Permissions. Users linked to this profile will have NO rights to the Button selected (i.e. the Button will be "grayed-out") regardless of the Override Code(s) linked on the User's User ID record or in the Override Codes field here.
When you have made your selection click Change All Button/Field Permissions to set all records in the DataGrid to the Code(s) selected.
DeleteOverride Codes (SAProfileScreenOnly_BulkButtonDataAccessCodes)
This field is applicable only if your Access Rights selection is With Matching Codes.Expand the Drop-down list to select the Override Code(s) you wish to link to Buttons you select. Multiple selection is allowed.
Override Codes are maintained in System Code Management. Type = Override Code.
To have access to a Button in this DataGrid that has Override Code(s) linked a User must have a matching Override Code linked to his/her User ID record. One match only is needed and multiple selection is allowed.
When you have made your selection click Change All Button/Field Permissions to set all records in the DataGrid to the Code(s) selected.
DeleteAllow User to Logout and Keep Session? (SAProfileDetails_AllowLogoutKeepSession)
Select this option to allow users linked to this profile to log out of RecTrac and select the option to keep their current session active. When this option is selected and a user logs out of RecTrac, the user can opt to keep the current session active or to end the session.
Deselect this option to force users to quit their current session at logout, which means each time that user logs back in, a new session will be started.
Notes:
- When changes are made to this option users must exit RecTrac and log back in for those changes to take effect.
- Regardless of your setting here a user can always terminate a RecTrac session by simply exiting the browser. In this event the session will remain open until the user logs back in or until the Session Cleaner Scheduled Event terminates it.
- Your setting in the Allow User to Start New Session when Open Sessions Exist? field determines whether a user will be allowed to continue an open session or be forced to start a new one.
Allow User to Start New Session when Open Sessions Exist? (SAProfileDetails_AllowUserStartNewSessions)
Select this option to allow users linked to this profile the option of continuing an open session at login (if one exists) or starting a new one.
Deselect this option to make users start a new session at login. When this option is deselected, users will always get logged into a new session. They will never be presented with option to Resume Old Session or Start New Session.
Notes:
- When changes are made to this option users must exit RecTrac and log back in for those changes to take effect.
- Your setting in the Allow User to Logout and Keep Session? field determines whether a user will be allowed to keep a session open at logout or be forced to end it.
Allow Use of VSI Design Toggle in Menu? (SAProfileDetails_AllowUseVSIDesign)
Select this option to allow users linked to this profile access to the Use VSI Design option located in the Support widget (the lifebelt" icon) on the Sidebar.
When this option is deselected users won't have access to the Use VSI Design toggle.
Use VSI Design allows users to switch from their custom screen to the standard Vermont Systems design "on the fly." This option here allows you to control which users have access to that option.
Notes:
- When changes are made to this option users must exit RecTrac and log back in for those changes to take effect.
- The ZZZ User ID is exempt from this Permission setting and always has access to the "Use VSI Design" option.
Enable 'The RecTrac Lab' in the Application Sidebar (SAProfileDetails_EnableRecTracLab)
Enable to display a RecTrac Labs link within the RecTrac menu, which enables your staff to learn RecTrac through free, Vermont Systems-created courses. Disable to remove the RecTrac Labs link from your RecTrac menu.
Note: This applies only to the Next Gen interface.
DeleteEnable VSI Support Link in the Application Sidebar (SAProfileDetails_EnableVsiSupportLink)
Enable to display a Customer Support link within the RecTrac menu, which brings your staff to the Vermont Systems Support portal. Disable to remove the RecTrac Support link from your RecTrac menu.
To access the Support portal, users must have a valid user name and password on file with Vermont Systems. Typically the user name and password are the email address and password on their User record in User Management.
Note: This applies only to the Next Gen interface.
DeleteEnable in-app Product Announcements (SAProfileDetails_EnableInAppProductAnnouncements)
Enable to display Vermont Systems-created announcements within the RecTrac home screen, as shown below. Disable to remove those announcements from the home screen.
Note: This applies only to the Next Gen interface.
DeleteEnable in-app Message Center (Coming Soon) (SAProfileDetails_EnableMessageCenter)
Enable to give users access to the RecTrac Message Center. The Message Center allows staff to send messages to patrons and receive replies directly through the application. Important communications are tracked and accessible from within the application and all communications remain securely stored.
DeleteMax Number Of SMS Messages Allowed Per Send (SaProfileDetails_NoOfSMSMessages)
Enter the max number of SMS text messages that a user, who is linked to this profile, can send at a single time.
THEN
Select your SMS Max Per Send - Allow Override option.
Enter '0' in this field if users linked to this profile are not allowed to send SMS text messages.
DeleteSMS Max Per Send - Allow Override (SaProfileDetails_SMSPerSendOverride)
Select this option to give users permissions to override the per send" limit on SMS text messages. For Example: The SMS per send limit is 10. The RecConnect yields 20 results. Users with this permission would be allowed to send all 20 text messages. Users without this permission would be denied and no text messages would be sent..
DeleteSMS Max Per Year - Allow Override (SaProfileDetails_SMSPerYearOverride)
Select this option to give users the permission to override your organization's yearly limit for SMS text messages. The yearly limit is defined on your License profile. For Example: Your yearly limit is 12 000 The RecConnect yields 200 results putting you over the yearly limit. Users with this permission would be allowed to send all 200 text messages. Users without this permission would be denied and no text messages would be sent..
DeleteAllow User to Update Evaluation Questions? - RecTrac Only Setting (SAProfileDetails_AllowEvaluationUpdates)
Select this option to allow users linked to this profile to update Answers to Evaluation Questions. Evaluation Question are updated under the Purchase History tab in Global Sales.
When this option deselected, Evaluation Questions will not display under the Purchase History tab in Global Sales.
DeleteCancel With Dependencies - Allow Override (SAProfileDetails_CancelWithDependencies)
Users with this Permission can bypass dependency restrictions, either during the sales process or from Purchase History. Dependency restrictions are designed to prevent the following types of transactions:
- Purchasing Item A to get a discount on Item B and then cancelling Item A
- Purchasing Item C because it is a prerequisite to purchasing Item D and then cancelling Item C.
- Etc…
Users with this Permission can bypass those restrictions and cancel the dependent item.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Cancel With Dependencies - Override Codes (SAProfileDetails_CancelWithDependenciesCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteBlind Refunds POS Inventory - Allow Override (SAProfileDetails_BlindRefundsPSI)
Users with this Permission can bypass restrictions on Blind Refunds for POS Inventory Items. Generally speaking, Blind Refunds are negative quantity transactions (i.e. -1, -2, etc…) not directly associated with a prior receipt or household for the item.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Blind Refunds POS Inventory - Override Codes (SAProfileDetails_BlindRefundsPSICodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteBlind Refunds POS Service - Allow Override (SAProfileDetails_BlindRefundsPSS)
Users with this Permission can bypass restrictions on Blind Refunds for POS Service Items. Generally speaking,Blind Refunds are negative quantity transactions (i.e. -1, -2, etc…) not directly associated with a prior receipt or household for the item.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Blind Refunds POS Service - Override Codes (SAProfileDetails_BlindRefundsPSSCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteBlind Refunds Visits - Allow Override (SAProfileDetails_BlindRefundsPMV)
Users with this Permission can bypass restrictions on Blind Refunds for Pass Visits. Generally speaking, Blind Refunds are negative quantity transactions (i.e. -1, -2, etc…) not directly associated with a prior receipt or household for the item.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Blind Refunds Visits - Override Codes (SAProfileDetails_BlindRefundsPMVCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeletePayment User - Allow Override (SAProfileDetails_PaymentUser)
Users with this Permission can change the Payment User ID linked to a transaction, at the time of the transaction or later.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Payment User - Override Codes (SAProfileDetails_PaymentUserCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeletePayment Date - Allow Override (SAProfileDetails_PaymentDate)
Users with this Permission can change the Date linked to a transaction, at the time of the transaction or later.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Payment Date - Override Codes (SAProfileDetails_PaymentDateCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeletePayment Drawer - Allow Override (SAProfileDetails_PaymentDrawer)
Users with this Permission can change the Drawer linked to a transaction, at the time of the transaction or later.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Payment Drawer - Override Codes (SAProfileDetails_PaymentDrawerCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeletePop Drawer - Allow Override (SAProfileDetails_PopDrawer)
Users with this Permission can pop the cash drawer without performing a transaction. Typically this done via a 'Pop Drawer' button.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Pop Drawer - Override Codes (SAProfileDetails_PopDrawerCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteEvent User Access - Allow Override (SAProfileDetails_EventUserAccess)
Users with this Permission have access to the Display Users Drop-down list in My Events and can opt to view "My User" events or "All User" events.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Event User Access - Override Codes (SAProfileDetails_EventUserAccessCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteDelete Other's Events - Allow Override (SAProfileDetails_EventUserDelete)
Users with this Permission can delete other User's Events from the DataGrid in My Events.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Note: Users can always delete their own events from the DataGrid.
Delete Other's Events - Override Codes (SAProfileDetails_EventUserDeleteCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteCredit Restrictions - Allow Override (SAProfileDetails_CreditRestrictions)
Users with this Permission can override/bypass Credit Restrictions between modules when processing sales. For Example: A household has a $l20 Credit in the Pass Visit Module. When processing an Activity enrollment for that household, a User with this Permission could apply the credit in the Pass Visit Module toward the enrollment.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Credit Restrictions - Override Codes (SAProfileDetails_CreditRestrictionsCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteMultiple Clerks in the Same Open Ticket - Allow Override (SAProfileDetails_OpenTicketMultipleClerks)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteMultiple Clerks in the Same Open Ticket - Override Codes (SAProfileDetails_OpenTicketMulitpleClerksCodes)
Users with this Permission can update POS Open Tickets linked to another User ID.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Tip User Access - Allow Override (SAProfileDetails_TipUserAccess)
Users with this Permission have access to the Display Users Drop-down list in Tip Processing and can opt to process tips for "My User" or "All Users."
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Note: Users can always process their own tips.
Tip User Access - Override Codes (SAProfileDetails_TipUserAccessCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteDocument User Access - Allow Override (SAProfileDetails_DocumentUserAccess)
Users with this Permission have access to the Display Users Drop-down list in Document Center and can opt to view documents for "My User" or "All Users."
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Note: Users can always view their own documents.
Document User Access - Override Codes (SAProfileDetails_DocumentUserAccessCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteDelete Other's Documents - Allow Override (SAProfileDetails_DocumentUserDelete)
Users with this Permission can delete other users' records in the Document Center provided they have permissions to view documents for "All Users" (i.e. provided they have permissions to Document User Access - Allow Override).
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Delete Other's Doucments - Override Codes (SAProfileDetails_DocumentUserDeleteCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteManaged Credit Card Profiles Access - Allow Override (SAProfileDetails_IncludeManagedProfiles)
Users with this Permission have access to the Records to Show Drop-down list in Epay Info Management (Household Update • Financial Info tab • Add/Change Credit Card Information button and can opt to view linked Credit Cards for "Linked Profile Only" or "Linked plus Managed Profiles."
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Managed Credit Card Profiles Access - Override Codes (SAProfileDetails_IncludeManagedProfilesCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteFuture Accrual Dates - Allow Override (SAProfileDetails_FutureAccrualDates)
Users with this Permission can Post Accrual with an End Accrual Date in the future.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Future Accrual Dates - Override Codes (SAProfileDetails_FutureAccrualDatesCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteRemove Items Sent to Kitchen - Allow Override (SAProfileDetails_ItemsSentToKitchen)
Users with this Permission can remove items from the shopping cart after they have been sent to the kitchen. This permission is used in a restaurant-style environment where items are queued to the kitchen (or bar) upon entry to the shopping cart. This permission allows you to remove them (i.e. cancel the order.)
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
Remove Items Sent to Kitchen - Override Codes (SAProfileDetails_ItemsSentToKitchenCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteCYMS Reservation Age Group - Allow Override (SAProfileDetails_CYMSReservationAgeGroup)
Users with this Permission can still make a hourly reservation even if a certain child's age is not a match for this facility's age group.
Select your Override option for this Permission.
- Yes - Users linked to this Permissions profile can override restrictions for this process.
- Yes - With Matching Codes - Users linked to this Permissions profile can override restrictions for this process provided a match is found between the code/codes in the accompanying Override Codes field and the code/codes linked in the Button/Miscellaneous Override Codes field for the user in User Update.
- No - Users linked to the Permissions profile cannot override restrictions for this process.
CYMS Reservation Age Group - Override Codes (SAProfileDetails_CYMSReservationAgeGroupCodes)
This field is applicable only if you are using the Yes - With Matching Codes Allow Override option.
Select the Override Code/Codes you wish to link to this field. In order to override the restriction users processing the transaction must have at least one matching code linked in the Button/Miscellaneous Override Codes field on their User ID record in User Management. One match only is needed.
For example you have the following Override Codes in your database: MANAGER and CLERK. The Cancel with Dependencies permission is set to Yes - With Matching Codes. The Override Code entered here is MANAGER.
- User ID LorettaM has the CLERK Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction LorettaM wouldn't be allowed to override the Cancel with Dependencies permission because the CLERK code on her User ID doesn't match the MANAGER code entered here.
- User ID PennyL has the MANAGER Permission Code in the Button/Miscellaneous Override Codes field on her User ID Record in User Update. When processing a transaction PennyL would be able to override the Cancel with Dependencies permission because the MANAGER code on her User ID matches the MANAGER code entered here.
Override Codes are maintained in System Code Maintenance. Type = Override Code.
DeleteMainTrac Permissions
Facility Default Record Permission (SAProfileDetails_MTFacilityDefaultAddRecord)
Expand the Drop-down list to select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
-
None- The user has no permissions for Adding Records. Users with this permission will be allowed to:
- Add a new record using an existing Default Record only (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record only (provided NO Default Records exist for this module).
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings Additional Settings etc...) and tabs (Core Fees* Rules* Questions Comments etc…) will be copied from the Default record.
"Default" status records to do not show up in Daily Processing DataGrids. You cannot register for reserve or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
* Separate Default Records for Fees and Rules can be created as well in their respective File Management program. Permissions must be set to add a Default Record and once added the default record can be linked as needed to any module.
DeleteEquipment Default Record Permission (SAProfileDetails_MTEquipmentDefaultAddRecord)
Expand the Drop-down list to select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
-
None- The user has no permissions for Adding Records. Users with this permission will be allowed to:
- Add a new record using an existing Default Record only (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record only (provided NO Default Records exist for this module).
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings Additional Settings etc...) and tabs (Core Fees* Rules* Questions Comments etc…) will be copied from the Default record.
"Default" status records to do not show up in Daily Processing DataGrids. You cannot register for reserve or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
* Separate Default Records for Fees and Rules can be created as well in their respective File Management program. Permissions must be set to add a Default Record and once added the default record can be linked as needed to any module.
DeleteTree Default Record Permission (SAProfileDetails_MTTreeDefaultAddRecord)
Expand the Drop-down list to select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
-
None- The user has no permissions for Adding Records. Users with this permission will be allowed to:
- Add a new record using an existing Default Record only (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record only (provided NO Default Records exist for this module).
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings Additional Settings etc...) and tabs (Core Fees* Rules* Questions Comments etc…) will be copied from the Default record.
"Default" status records to do not show up in Daily Processing DataGrids. You cannot register for reserve or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
* Separate Default Records for Fees and Rules can be created as well in their respective File Management program. Permissions must be set to add a Default Record and once added the default record can be linked as needed to any module.
DeleteStreet Default Record Permission (SAProfileDetails_MTStreetDefaultAddRecord)
Expand the Drop-down list to select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
-
None- The user has no permissions for Adding Records. Users with this permission will be allowed to:
- Add a new record using an existing Default Record only (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record only (provided NO Default Records exist for this module).
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings Additional Settings etc...) and tabs (Core Fees* Rules* Questions Comments etc…) will be copied from the Default record.
"Default" status records to do not show up in Daily Processing DataGrids. You cannot register for reserve or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
* Separate Default Records for Fees and Rules can be created as well in their respective File Management program. Permissions must be set to add a Default Record and once added the default record can be linked as needed to any module.
DeleteUtility Default Record Permission (SAProfileDetails_MTUtilityDefaultAddRecord)
Expand the Drop-down list to select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
-
None- The user has no permissions for Adding Records. Users with this permission will be allowed to:
- Add a new record using an existing Default Record only (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record only (provided NO Default Records exist for this module).
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings Additional Settings etc...) and tabs (Core Fees* Rules* Questions Comments etc…) will be copied from the Default record.
"Default" status records to do not show up in Daily Processing DataGrids. You cannot register for reserve or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
* Separate Default Records for Fees and Rules can be created as well in their respective File Management program. Permissions must be set to add a Default Record and once added the default record can be linked as needed to any module.
DeleteMaterial Default Record Permission (SAProfileDetails_MTMaterialDefaultAddRecord)
Expand the Drop-down list to select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
-
None- The user has no permissions for Adding Records. Users with this permission will be allowed to:
- Add a new record using an existing Default Record only (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record only (provided NO Default Records exist for this module).
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings Additional Settings etc...) and tabs (Core Fees* Rules* Questions Comments etc…) will be copied from the Default record.
"Default" status records to do not show up in Daily Processing DataGrids. You cannot register for reserve or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
* Separate Default Records for Fees and Rules can be created as well in their respective File Management program. Permissions must be set to add a Default Record and once added the default record can be linked as needed to any module.
DeleteTask Code Default Record Permission (SAProfileDetails_MTTaskCodeDefaultAddRecord)
Expand the Drop-down list to select your Default Record Permissions for this module. The selection you make determines the options users linked to this Permissions profile will receive when attempting to Add a new record in File Maintenace for the Module selected.
-
None- The user has no permissions for Adding Records. Users with this permission will be allowed to:
- Add a new record using an existing Default Record only (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record only (provided NO Default Records exist for this module).
-
Allow Blank Record Choice- The users can add new records using either an existing Default Record or adding a new 'regular' File Management record. Users with this permission will be allowed to:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
-
Full Prompt- Whenever adding a new File Management record for this module, users with this permission will be prompted. Users can either:
- Add a new record using an existing Default Record (provided at least one Default Record exists for this module).
- Add a new 'regular' File Management record regardless of whether Default Records exist for this module.
- Create a new Default Record for this module. This is the only option that allows for the creation of new Default Records.
Default" status allows you to create exact-copy records upon clicking the Add button from the File Maintenance DataGrid for this module and selecting one of existing Default Options (provided at least on exists). This creates an exact copy of the "Default" record with exception that the copy's Record Status is Active instead of Default. This allows you to save substantial time when adding new records to your database since all settings on all panels (Core Settings Additional Settings etc...) and tabs (Core Fees* Rules* Questions Comments etc…) will be copied from the Default record.
"Default" status records to do not show up in Daily Processing DataGrids. You cannot register for reserve or purchase a "default" record. They exist for the purpose of being copied only. If at any time you change the status of a Default record to Active or Inactive it will become a "regular record" in your database and thus appear in Daily Processing DataGrids if applicable.
* Separate Default Records for Fees and Rules can be created as well in their respective File Management program. Permissions must be set to add a Default Record and once added the default record can be linked as needed to any module.
DeleteWork Order Approval Codes (SAProfileDetails_MTWOApprovalCodes)
For use with the MainTrac module only.
Click the Combo Box icon to select the Work Order Approval Codes for users linked to this Permissions profile. Work Order Approval Codes allow you to have different levels of approval to determines when a Work Order (WO) is "fully approved." For Example: You have two (2) Approval Codes: M=Manager and P=General Personnel. Employees with "P" approval rights can approve a WO but the WO must be also approved by a Manager. Therefore another employee with a "M" approval code must also approve the WO before it becomes "Approved." When a WO is "P" approved it moves from the status of "New" to "Reviewed." When the WO is "M" approved it moves from "Reviewed" to "Approved."
Note: In order to be used Work Order Approval System Codes need to be linked on the MainTrac tab of your Static Parameters profile.
Work Order Approval Codes are System Codes. Type = Work Order Approval.Data Access profile