TradingView Username

This page is for the little field that can make access feel much more complicated than it looks.

Your TradingView username is not a display name for Axiom. It is the username Axiom uses when it needs to send TradingView product access to the right place. If that username is missing, stale, or mistyped, the purchase can be fine while delivery still feels wrong.

Use Account to set the active TradingView username. Use Access after saving when the question becomes, "Did delivery move, fail, retry, or finish?" Use Products when you need to check whether the product or package is attached to your Axiom account.

Those are three different checks. Keeping them separate saves you from trying to make one screen answer the whole story.

Before you save a username

Start here:

• You need to be signed in before the dashboard Account page opens.

• Use the Axiom account whose access you are trying to check.

• Know the exact TradingView username you want Axiom to use.

• Enter the TradingView username itself. Do not swap in your Axiom email or Axiom display name because it feels account-related.

• If you are checking delivery after a purchase or username change, keep Access nearby.

• If you are checking whether the account owns the product, keep Products nearby.

The Account page can tell you which username is active. It does not prove that TradingView delivery has completed. That proof, or at least the next visible state, belongs on Access.

If you recently saved the wrong username, keep the old one in mind. It may matter when you read Username history, and it is useful context if support needs to look at a failed or mismatched delivery state.

What you should know when you are done

After using this page, you should be able to say:

• which TradingView username is active now;

• whether the save changed anything;

• why older usernames still appear in history;

• why changing the username affects future access routing but does not promise an instant move of already completed access;

• what Saving... means, and why it is not a TradingView delivery status;

• where to check delivery after saving;

• when the next step is Retry, waiting on an open task, checking Products, or contacting support.

The goal is not to make the username field feel bigger than it is. The goal is to stop a small field from turning into a mystery.

What the active username is for

Axiom needs an active TradingView username when it has TradingView access work to deliver for your account.

The important word is active. You may have more than one saved username in your account history, but only the active one should be treated as the current destination for new delivery work.

That is the boundary to keep clear: the active username tells Axiom where new or refreshed access work should go. It does not erase the fact that older work may already have happened somewhere else, and it does not turn a completed TradingView-side state into an instant transfer.

Think of it this way:

If Products shows the product but TradingView does not, that does not automatically mean the purchase failed. It may mean the account inventory and the TradingView delivery work are at different points in the process. Check the active username, then read Access.

Where to set it

Open Account from the dashboard navigation.

At the top of Account, the summary card named Active TradingView username shows the username currently saved for delivery. If no active username is saved, it can show Not set.

Then find the section named TradingView username.

That section shows:

• Current username

• the Username field

• the Enter TradingView username placeholder

• Save username

• Saving... while the save is still running

• a result message under the form after the save returns

• Username history

Use the Username field when Current username is missing or wrong. Choose Save username, then wait for the button to stop saying Saving... before deciding what happened.

Saving... only means the Account form is still submitting. It is not the same as Queued, In progress, Completed, or Failed on Access.

Save or update your TradingView username

Use this sequence when you need to set the username for the first time or correct the active one.

1. Open Account.

2. Read the Active TradingView username summary card.

3. Find TradingView username.

4. Check Current username.

5. Enter the correct TradingView username in Username.

6. Select Save username.

7. Wait while the button says Saving..., if it appears.

8. Read the message below the form before taking the next step.

9. Review Username history so you know which username is active now.

10. Open Access if you need to check delivery.

Do not keep pressing save while the button is pending. The useful next information is the result message, not another click.

If you are correcting a username after a failed delivery attempt, saving the corrected username is only the Account step. The Access step still matters, especially if a failed row offers Retry.

Read the save result

The message below the username form matters. It tells you what happened to the saved username, not everything that has happened inside TradingView.

A successful username save is a real step. It gives Axiom the active destination for future TradingView access work. But it is not the same thing as seeing the product inside TradingView immediately.

That gap is where a lot of the stress lives. You did the Account part, and Access may still need time to show whether delivery is open, completed, failed, or retryable. Do not treat that gap as proof that the purchase broke. Read the visible state first.

What changes after saving

When you save a different TradingView username, Axiom changes which username is active for future TradingView access routing.

If your account already has active product access, that change can cause delivery work to be refreshed for the new active username. You may see Access change after the save. Newer access work may appear. Older open work may no longer be the work that matters. If there was a previous active username, Axiom may also need to clean up access tied to that previous username.

That can look noisy for a minute. Noise is not automatically bad news. A username change can create fresh delivery state because the system now has a different destination to work with.

That does not mean every old TradingView-side access item instantly moves the moment the form saves. The supported reading is more careful:

• Account says which username is active now.

• Access says what delivery work is open, completed, failed, or retryable.

• Products says whether product or package access is attached to the Axiom account.

If you changed the username because access was sent to the wrong TradingView account, do not stop at the success message. Go to Access and read the current rows. That is where you can see whether delivery is catching up, failed, or asking for a supported next step.

Read username history

The Username history section is there so you can see usernames that have been saved on the account over time.

If no username has been saved, it can show No usernames added.

When history exists, each row tells you whether that username is current or old context.

History is not a list of usernames receiving new access at the same time. Treat it like a record of where the account has pointed before.

If you intentionally return to an older TradingView username and save it again, that old username can become active again. After that, history may look familiar, but the important question is still simple: which row is active now?

When the question is delivery, move from history to Access. History explains the past. Access shows the current work.

Check Access after updating

Open Access after saving when you need to know whether delivery resumed, failed, or still has work open.

At the top of Access, start with the summary:

• TradingView username shows the active username Access is using for delivery context.

• Open access tasks counts delivery work that has not finished.

• Needs attention points you toward failed work.

Then read the Access profile:

• Active username

• Saved usernames

• Access events

The field to trust first is Active username. Saved usernames is context. It is not proof that several usernames are being used right now.

If Open access tasks is not zero, read those rows before assuming something is wrong. Open work is still work. If Needs attention is not zero, start with the failed rows and their messages.

Read the access rows

Access rows are where the delivery state gets concrete.

A row can show:

• task action labels such as Grant access or Revoke access;

• the status;

• the product name;

• the product type;

• when it was requested;

• attempts;

• queue state such as N ahead, Complete, or N/A;

• a failure message when one exists;

• View subscription when subscription context is available;

• Open TradingView when a TradingView product link is available;

• Retry when the failed row can be retried by you.

The visible statuses are:

• Approved

• Queued

• In progress

• Completed

• Failed

Read the row like a work order. Match the product name, status, requested time, and message before deciding what to do.

If a task is Approved, Queued, or In progress, it is still open. That is not the same thing as failed. If it is Completed, the Axiom delivery task has finished, but you should still check TradingView from the right TradingView account. If it is Failed, read the failure message and look for Retry.

The row is more useful than a hunch. Product name, action, status, requested time, attempts, queue, and message together tell a better story than any one label by itself.

Use Retry only when Access offers it

Retry is not a general-purpose button. It appears only when the failed task is in a state the website allows you to retry.

Before using Retry, check:

• the active TradingView username is set;

• the active username is the one you actually use on TradingView;

• the failed row belongs to the product you are trying to access;

• the row does not already point you toward support instead.

After you use Retry, read Access again. A retry sends eligible delivery work back into the process. It does not prove the product is already visible inside TradingView.

If the failure was caused by a bad TradingView username, the useful order is: correct the active username on Account, return to Access, then use Retry only if Access offers it.

If a failed row does not show Retry, do not hunt for a hidden action. The absence matters. Read the message, compare Products if needed, and contact support when the visible state does not give you a safe self-serve move.

Where Products fits

Use Products when your real question is whether the product or package is attached to your Axiom account.

Products can show:

• Active items

• Access queue

• Current products

• product or package rows

• product-level fulfillment status

• Open TradingView when a TradingView link is available

Products is not where you change the TradingView username. It is also not the final word on TradingView delivery.

The clean split is:

• Account answers, "Which username is active?"

• Products answers, "What does this Axiom account have?"

• Access answers, "What is happening with TradingView delivery?"

So if Products shows the product but TradingView still does not, the next check is usually Access. If Access shows open work, read the status. If Access shows Failed, read the failure message and use Retry only if the button appears. If Products shows access but Access has no delivery state that explains what you see, that is the kind of mismatch support can investigate.

If this looks stuck

Use the visible state to choose the next honest move.

The useful move is usually smaller than panic wants it to be: confirm the active username, read Access, compare Products, then decide whether the website gives you a next action.

When to contact support

Contact support when Account, Access, and Products stop giving you a safe self-serve next step.

That usually means:

• the username save keeps failing with the same visible message;

• Account shows the correct active username, but Access does not show a delivery state you can act on;

• Access shows Failed and no Retry;

• you corrected the active username, used Retry when it appeared, and delivery still fails;

• Products shows the product, but Access does not explain why TradingView access is still missing;

• you recently changed usernames and cannot tell which task belongs to which username;

• the dashboard pages show facts you cannot reconcile from what is visible.

Support can investigate mismatched or failed visible state. Support is not an instant-access button, and it is not a way around account, payment, or TradingView confirmation.

Use Contact and send the plain facts:

• the email on your Axiom account;

• the active TradingView username;

• the previous TradingView username, if you recently changed it;

• the product or package name;

• what Account shows for Current username;

• what Access shows for task action, status, queue, attempts, and failure message;

• whether Retry is visible;

• what Products shows for the product;

• what you expected to see inside TradingView.

Avoid sending only "access is broken." That may be exactly how it feels, but the useful trail is the page, the username, the product, the row status, and the message. If there was an old username in the story, include it. If Retry was or was not visible, include that too.

Related pages

• Dashboard

• Account

• Access

• Products

• Contact

• Account Profile

• Access Delivery and Fulfillment

• Products and access

• Dashboard overview