
Sabre Red Web sign-in credentials explained
The Sabre Red Web sign-in screen asks for four values, and each one answers a different question about the person signing in. The username and password together identify an individual travel professional. The PCC identifies the agency or corporate office that person is working on behalf of. The authenticator code confirms that the individual holding those credentials is physically present at the moment of sign-in. None of the four is checked on its own, which is the detail that trips people up. A perfectly correct password is still refused when the PCC belongs to a different office, and a correct PCC is still refused when the username has been deactivated by the agency.
How the four values work together
Think of the username as the person, the password as proof of that person, the PCC as the booking context, and the authenticator code as proof of the moment. Because the booking context is chosen at sign-in rather than remembered on the account, a travel consultant who covers two branches during the week uses the same username and password but a different PCC on each day. That design keeps bookings filed under the right agency record, and it also explains why the PCC is the field most often entered from memory and most often wrong. If you are unsure which PCC applies to a shift, ask the agency administrator before you try to sign in rather than working through the possibilities on the form.
Reference list of sign-in terms
The entries below explain each value in the order it appears on the form, what it controls, and the mistake people most often make with it.
- Sabre ID username
- The unique identifier issued to an individual travel professional. It is not an email address, so the sign-in form asks for it separately rather than treating the two as interchangeable.
- Why it matters: Bookings, ticket queues and agency permissions are attached to this identifier, so a shared or borrowed username files work under the wrong person.
- Common mistake: Typing an email address, or a username issued by a previous agency that has since been deactivated.
- Password
- The secret phrase that proves the person entering the username is the owner of that Sabre ID. It is managed by the individual and changes independently of the agency record.
- Why it matters: A password changed on another device takes effect immediately, so the version saved in a browser may already be out of date.
- Common mistake: Reusing a password saved months ago, then assuming the PCC is the problem when the sign-in is refused.
- PCC (pseudo city code)
- A short code that identifies the agency or corporate travel office a booking belongs to. It is chosen at sign-in, which is how one person can work for more than one office with a single username.
- Why it matters: The username and PCC are validated as a pair, so a correct code for an office you are not assigned to will still be refused.
- Common mistake: Using the code from a previous branch, or a code read back to a colleague over the phone and mistyped by one character.
- Authenticator code
- A six-digit code generated on the phone or device enrolled for the account, valid for roughly thirty seconds before it expires and a new one replaces it.
- Why it matters: It is the only field that proves presence at the moment of sign-in, which is why it cannot be saved or reused on a later day.
- Common mistake: Waiting for the next code and typing an expired one, or reading the code from a different account in the authenticator app.
- Agency administrator
- The person at the agency who issues usernames, confirms which PCC applies to a shift, and can reset an authenticator enrolment when a phone is replaced.
- Why it matters: Most blockers that look like a sign-in fault are actually a record that needs updating at the agency level, which only an administrator can do.
- Common mistake: Repeatedly retrying the form instead of asking which PCC and username pairing is current.
Questions people ask most
What is a PCC in Sabre Red Web?
The PCC (pseudo city code) is a short code that identifies the agency or corporate travel office a booking belongs to. It links the person signing in to the correct agency record, which is why it is requested alongside the username rather than set in a profile.
Why do I need an authenticator code as well as a password?
The password proves who you are, and the authenticator code proves the person holding the password is the one signing in. The code is generated on a device you enrolled and changes roughly every thirty seconds, so a password alone is not enough to reach a booking workspace.
What should I do if my PCC does not match my Sabre ID?
Stop and check with the agency administrator. A mismatched pairing is refused even when both values are typed correctly, because the record has to match the agency you are working for that day.
Practising the four fields
Reading about the fields is useful, but the order they are typed in is what most people need to rehearse. The practice sign-in on this site reproduces the form so the sequence can be worked through without risking a lockout on a live agency account. No password is ever captured or stored, and no real sign-in takes place.