I purchased Sword Coast Adventurer's Guide and none of the classes are appearing for me to use

I purchased Sword Coast Adventurer's Guide and now the classes I wanted to use are not in my options

Do you mean subclasses? (That book does not contain any new classes.)

If so, there are two main things to look into:

1. Go here and see if it says your entitlements are synced. If it says they're not, click the button there to sync them.

2. This book was written for the 5e rules. Many of the subclasses in it have been superseded in the 5.5e rules by updated versions. In these cases, if you've selected the 5.5e version of a class, you won't be able to use the 5e version of the subclass, and if you don't own the 5.5e content that includes it, you won't be able to use the 5.5e version either. In that case, you'd need to remove the 5.5e class and choose the 5e class instead; then you'll be able to select the 5e version of the subclass.

Specifically:

The following are still eligible for use in the 5.5e ruleset
---
Barbarian - Battlerager
Cleric - Arcana Domain
Monk - Long Death, Sun Soul
Paladin - Oath of the Crown
Rogue - Mastermind, Swashbuckler
Sorcerer - Storm Sorcery
Warlock - Undying

The following have been replaced by 5.5e versions of the subclasses
---
Battlerager - Totem Warrior (options provided, replaced by Wild Heart)
Fighter - Purple Dragon Knight (replaced by Banneret)
Wizard - Bladesinger

Also make sure the 5e Expanded toggle is turned on in your character settings.

Quote from spamandtuna >>

Purple Dragon Knight and Bladesinging actually are available for the 5.5e classes (in addition to their 5.5e replacements). Totem Warrior is the only one that requires the 5e class.

 That feels like a bug...

Whether the people running the site left it up intentionally or not doesn't impact whether or not it's a bug, though. It's both inconsistent behavior for the site (having some legacy subclasses in the 5.5e class bases and not others) and incorrect behavior according to the 5.5e rules to display that at all.

Quote from Athanar90 >>

Whether the people running the site left it up intentionally or not doesn't impact whether or not it's a bug, though. It's both inconsistent behavior for the site (having some legacy subclasses in the 5.5e class bases and not others) and incorrect behavior according to the 5.5e rules to display that at all.

I think removing them would be frustrating for people who created characters using those combinations (e.g. a 5.5e Fighter with the old Purple Dragon Knight subclass) in the interim between the release of the 5.5e Player's Handbook and the release of Heroes of Faerun. Those people would suddenly find their characters didn't work unless they bought the newly released book.

If I remember right, the site handled such characters fine whenever a UA subclass was removed. If leveling would cause problems, I suppose that's a different issue, but the inconsistency is still not great to have.

Quote from spamandtuna >>

 A bug is, by definition, something that’s not working as intended. Since this is working as intended, it’s definitely not a bug.

 There's multiple types of "as intended" though. In this instance, those subclasses don't qualify for use according to the 5.5e rules, which makes their inclusion a bug in terms of gameplay rules.

I think the confusion is that Sword Coast Adventurer’s Guide doesn’t really add new base classes — mostly subclasses, backgrounds, spells, and options for existing classes.

Usually if content isn’t showing up, it’s because:

• the source isn’t enabled in character creation
• legacy content is hidden
• or the campaign/settings only allow certain books

I’d check the character builder content toggles first.

The old bladesinger is available, but has the Legacy tag. This seems like the correct solution to me: it's available for those who have purchased it and the 2024 PHB, but there's also a clear indication that it is no longer the official version of the subclass.

The puprle dragon knight does not have the Legacy tag, which probably is  bug.

Quote from Athanar90 >>

Whether the people running the site left it up intentionally or not doesn't impact whether or not it's a bug, though. It's both inconsistent behavior for the site (having some legacy subclasses in the 5.5e class bases and not others) and incorrect behavior according to the 5.5e rules to display that at all.

 That's literally the definition of a software bug—an unintended behavior. Inconsistency doesn't make it a bug; poor UX perhaps, but not a bug.