Character Nameplates not visible by other players, even with player permissions set to "See"

As the title says, I cannot get the player tokens set so other players can see the names. I've checked name plate, set player permissions to see. Logged out, back in several times, even added the characters sheets to the other players' journals. I've done this on all my other campaigns. I haven't check back to see if the other campaigns are still holding the nameplates, but I can say right now I simply cannot get the nameplates to be visible to the other players. They can see their own, but only their own. Obviously I'm doing something wrong... who can help me here?

It's likely due to a bit of unfortunate design. Are you just clicking the "see nameplate" button, or also going into thee popup menu just above that to carry over the permissions to players? "Edit" gives sight to anyone who has edit control on the character. "See" lets everyone see.

Yes, I have "See" under general permissions checked as well as the nameplate box checked. It is still working in my other campaigns (which have been around for a while). The one I'm having troubles with I just started this past weekend. 

Well that should certainly do it. Here are some other things to check/try: Make sure players are on the same page you are viewing, (They should be on the player flagged page unless you have used the "Split the Party" function. Check to make sure these are the settings on the token in place , not just the default token.* Use a  Dummy Account  to check the player experience first hand, to eliminate any miscommunication. * You probably know this, but I'm putting it in a footnote for completeness' sake. The order of operations in setting up a default token is critical. Unless the default token is set as the last step, you will not get expected results: Here is the wiki article on  Linking Tokens to Journals Here is a  video  which demonstrates the procedure

Yes, I have checked it from a player's account as well. This is an official 5e module... could something have been activated via campaign settings? I appreciate your help. This certainly has me scratching my head.

Make sure the tokens are on the token/object layer rather than the map layer?

There is nothing in campaign settings that would override your manual settings. Since the forum is not flooded with reports on this, it almost certainly has to be something that is being overlooked. When logged is as a player, you could see the tokens, but not their names? Was this true of all tokens, or just some? Are you using any third party extensions that might affect the behavior of Roll20. Ah! Are you by any chance using the Health Aura Colors script? That script is very problematical and has many default settings that have nothing to do with its stated purpose, including affecting nameplate visibility.

No to the Health Aura Colors. We are using beyond 20, but the same is true for the other campaigns. I agree, there has to be something I am overlooking. I did make sure they are on the Token Layer. I only have one other profile to use to test, but none of the others are visible. The last time we played, I couldn't get the players to see each other either. I may just try creating a new campaign and see if I can get them to display correctly as a test.

I seem to have a similar problem, so following with interest.

I have a few clarifying questions.  I see in your screenshot above that the token is assigned to a character sheet.  What character sheet are you connecting to?  Also, if the token is not connected to a character sheet can your players see the nameplate?  This would eliminate the character sheet from consideration or not. Can you clarify what api scripts, if any, you are using in your game?

Having to do this twice is incredibly annoying

@Adam J Not running any API scripts on this campaign. It is using the Phandelver official module here on Roll20. The game was created from "create campaign" feature from the marketplace. Character sheets were added but no other modifications have been made. Interestingly enough, I just dropped two dog tokens in there to see if your theory on the character sheet is correct. One I attached to one of the players' character sheets. When logged in on my dummy account, I can see the nameplate of the one that ISN'T connected to a character sheet. The one that is attached to a character sheet does not display the nameplate. So it seems like something to do with the character sheet perhaps? Also of interest, simply removing the character sheet link (turning the token back to none) isn't enough to get the nameplate to show. Running the dummy account on a different browser. Only putting a fresh token in seems to work.

Bill said: I seem to have a similar problem, so following with interest. Ok, I found something that worked to fix this, though I'm not sure what the actual problem is. If I copy and paste the token, everyone can now see the nameplates. The original tokens however I cannot get to display. So perhaps a glitch of some type dealing with being linked to a character sheet? Very odd, but try copying and pasting the tokens and see if that works. It did for me. Doesn't explain the issue, but at least I can get it to work.

Does this happen in a test game with no APIs or extensions? (I have no idea of the capabilities of Beyond20),

Beyond 20 is a browser extension. I haven't tried a browser without roll20 yet. It may be a day before I can get around to removing the extension and trying. I'll let you know when I do.

I use Beyond20 for all my games and I do not see the issue.  I suspect it is something to do with some hidden setting/token setup from the "create campaign" preconfigured module.  I don't know what setting, but this seems to be the only thing that is different.  Especially since new tokens you drag into the game seem to work as well as copy pasted ones with new IDs.  But I can't take it further than that sorry to say. I'm glad you found a workaround.

FWIW, whenever I suggest turning off an extension for diagnosing a problem, I am never recommending that someone do not use such extensions, so long as they do not break any copyright laws or TOS (which neither Beyond20 or VTTES do, to my knowledge). It just that they are pretty much "after-market" products and can disguise the source of an issue. It's just one less variable to wade through. Same thing for Browser choice. I recommend using a supported browser while trying to debug something, but whatever works best for a user is de facto the "right choice".