George Peppard

When browsing your VA's member list, or leaderboards, you may come across some members with a  badge.
This badge exists to help you identify genuine vAMSYS staff accounts, and provide some explanation about why you cannot perform certain actions to these accounts.
Who are ?
The vAMSYS team is made up of several sub-teams that perform different roles across the platform. The  badge is shown on the profiles of members of the team who have superuser access to the platform. Currently, this access is given to the vAMSYS platform development team, and the vAMSYS Community Support team.
Accounts bearing this badge may have a normal pilot ID, or they may have a strange-looking ID such as "RYR-George". No matter the pilot ID, only people with the  badge are vAMSYS platform superusers.
The vAMSYS team members act independent of any VA, and we never make decisions on behalf of your VA management team. We don't reinstate pilot accounts, maintain the VA in any way, or review PIREPs.
What is a superuser?
vAMSYS superusers have access to every page of every VA, and this extends to VDS (the route management area) and Orwell (the VA back office and management area). They also have access to Aeolus, which is the vAMSYS platform-wide administration panel, and contains details on airlines and users. When a superuser logs into a VA, the things they can see and do (pretty much) model that of the VA owner.
Some data needs an even higher level of permission to view or edit. If this is the case, then the data can only be seen or edited by a database admin (referred to in some places as a platform administrator, or a platform manager). Not all DB admins are , yet some  are platform administrators. There are currently only two members of the vAMSYS team with DB admin access. They can be contacted via the support desk if necessary.
vAMSYS team members only access your VA's data where there is a need to do so. They will never share the data with anyone outside the vAMSYS staff team. If vAMSYS team members choose to fly for your VA, they will fly as normal pilots do, will be subject to normal scoring and PIREP approval/rejection rules, and will not manually override decisions made by the automated system. If you would rather a team member did not fly for your VA, you can either contact them directly (e.g. via Discord or email), or you can raise a ticket with vAMSYS Customer Services.
Who are these strange accounts in my new VA?
Superusers are added to your VA when it is created so that they can automatically see and log in to the VA, for example to provide support or investigate a bug report. Superusers added to your VA will have the badge automatically too. It is not possible to remove a superuser from your VA - this is similar to how it is not possible to remove staff from a VA without removing their staff permissions first.
Can I become a superuser?
Superuser privileges are only granted if a member of the team's role requires them. We recruit members for these roles directly, so it is not possible to apply for these roles.

We accept the following payment methods:
Visa Mastercard American Express Discover (including Diners Club) China UnionPay JCB Cartes Bancaires Interac We do not accept PayPal.

vAMSYS 3.8.0 added the functionality to allow the "force airline" parameter. This allows any request to vAMSYS to have an optional parameter appended to the URL which will force the session to fall under your VA before further page logic is processed.
How do I add this to my links?
Take a simple link - for example, https://vamsys.io/resources/mycustompage. Ordinarily, this would result in a 404 if a user accessed it via any airline other than yours, which could cause confusion among your pilots, especially if they are a member of multiple VAs.
Not to worry though - we just need to add the force airline parameter to the URL: https://vamsys.io/resources/mycustompage?select=ABC.
This will force the user, when navigating to this page, to have my airline (in this case, the airline with the prefix ABC) selected - and they will be able to access the page.
How does this work?
For information on how this process works, see the following flow chart:

At the time of writing, the files provided by VASchedules are not in a compatible format, so they do not work with our importers.
If you're a new VA to the platform, we strongly recommend you read this before you import anything!
vAMSYS cannot accept liability for the contents of these external websites, and we cannot provide support for their products. We encourage you to contact their support teams and inform them that the files are not natively compatible with v3 importers.

What is vAMSYS?
vAMSYS is the Virtual Airline Management System. We're the leading VA management solution by users and featurebase in the industry and we provide hosting and second line support services for over 60 virtual airlines (and counting) - which your VA might be one of.
vAMSYS is a service provider that provides support to paying customers (i.e. the VAs that are hosted on our platform). We're also responsible for the maintenance of common account details (such as name or email address) and other details that is related to you as a user, and not as a VA pilot. For pilots, we provide a convenient way to join multiple VAs with the same credentials.
vAMSYS is not in itself a virtual airline or an alliance of airlines. We do not provide first-line support to VA pilots. We are not responsible for rejected flights or PIREPs, the route network on the VAs we host, VA policies or the appointment and management of the staff of each VA. We also can't intervene on most data held regarding a VA without permission from VA management (even if we did want to accept your PIREP - we can't!). We also cannot reinstate your pilot account if it has been removed.
For the purposes of data protection legislation, when you provide your information on the vAMSYS website, vAMSYS LTD is the data controller. We share your data with VAs you are a member of for the purposes of them providing a service to you. You can find more details in the vAMSYS Terms and Conditions and the Privacy Policy, at https://vamsys.io/legal
Why we don't have a list of all VAs
Many users misinterpret vAMSYS as a platform for advertising VAs, or think that vAMSYS operates or has a say in the management of the VAs that use our platform. This is simply not the case.
By us choosing to show you VAs you are not a member of, we would cross a very distinct line between being a service provider and an advertiser. The former we are, the latter we are not.
But why do you show me VAs on the select page I am not a member of? - we hear you ask. It's very important to note that the VAs shown to you are not because vAMSYS has chosen to do so, or because we "favour" certain VAs. VAs shown to you on the select page are shown as one or more of the VAs you are a member of has a "pilot sharing agreement" with the VA being offered to you. VAs choose what other VAs to advertise - not vAMSYS.