A playlist label is not an account credential
The name used to identify a playlist inside a player can be a local label rather than the username that authenticates an account.
Keep the roles of the fields distinct. A clear household label should not contain a password, token or private link. If the interface differs from the guide, stop and identify the actual account method instead of moving credentials into whichever field happens to be visible.
A practical check
- Read each field label
- Use a clear non-sensitive playlist label
- Enter credentials only through the intended legitimate method
Related: hls basics · player service
Why a working playlist URL should stay private
A playlist address can include information tied to account access, so treat it as private rather than a harmless public example.
Do not post a working URL, QR code or exported player configuration in a public question. Keep the error message visible while concealing the access-bearing material. A description of the account method is usually more useful for a public discussion than a functional credential-bearing link.
A practical check
- Conceal the complete access URL
- Remove tokens and usernames from screenshots
- Use the agreed private support channel for necessary account details
Related: support handoff
Check copied credentials without exposing them
Copied values can include unintended spaces or characters, so inspect them privately in the intended input fields.
Do not publish the value in a screenshot to demonstrate the problem. Record the actual field and error stage instead. If the account method is uncertain, establish that method first; repeatedly trying the same value in unrelated app screens is not a useful diagnosis.
A practical check
- Confirm the intended field
- Check accidental leading or trailing characters privately
- Report the error without disclosing the value
Make a support screenshot useful and private
A useful support image shows the symptom and the interface context without exposing account access or customer records.
Crop or redact credentials, playlist URLs, tokens, customer names, balances and identifying device details before distributing the image. Keep the error text and app identity legible. Retain a private original if needed, and do not assume that a partial visual crop has removed hidden metadata or every sensitive area.
A practical check
- Inspect the full image
- Hide access and customer details
- Keep the actual error and app identity readable
Related: support handoff
Store, player and service passwords have different owners
A device may ask for credentials at several stages, including its app store, a player licence and a service account.
Read the identity of the screen before signing in. The legitimate service credentials should not be treated as a universal password for the television or every app. A support report should describe which component is asking for access, without revealing the private value.
A practical check
- Identify the screen's service
- Use the correct account for that component
- Avoid posting credentials in a general discussion
Related: player service
Questions answered
Should a playlist name contain my password?
No. Use a non-sensitive label and keep credentials in their intended private fields.
Is changing a local playlist label the same as changing account access?
Not necessarily. A label and an authentication credential have different roles.
Is a playlist URL always safe to post because it is only a link?
No. It can contain access information and should be treated as private.
Can a QR code reveal the same information as a visible URL?
Yes. Conceal access-bearing QR codes as well as readable text.
Does every sign-in form expect the same account format?
No. A player, store and service may use different account methods.