all users can access their battery via the equivalent battery link, which uses the battery name as a hash (so it's not discoverable) and then user / worker data is generated and saved as a variable in the user's session. I don't see a good use case to generate a single link to do the equivalent!
all users can access their battery via the equivalent battery link, which uses the battery name as a hash (so it's not discoverable) and then user / worker data is generated and saved as a variable in the user's session. I don't see a good use case to generate a single link to do the equivalent!