Features & Suggestions / Dedicated server - please more confidential environment
<< < > >>
Reply to this Thread
1/11/2010 12:52:50 PM Reply with Quote

Quote:
Originally posted by Gyorgy Bosz 
Is this means if we will change our settings at PersonalPage-URL then the Personal Page and the Conference links both will be appear in mydomain.com format? (Of course I need to point DNS to nefsis server before) Or Do we need to change at My Deployment-General-Domain for conference link?


This is our intent. We're in the process of reviewing how conference links are created and shown, so what you see right now may not be reflected in the software currently. It should be much more uniform in the near future.

Quote:
Originally posted by Gyorgy Bosz 
Not definitelly same. I asked my users to send link without &password.... The password for participation on a meeting is part of trustship of the customer and avoid unauthorized participation. As I told You we are a law office. We using conferences (for example) to providing and documenting stakeholder meetings, where only authorized people should be participate. The password for this conferences are separately handled. Not in the mail of invitation and reminder. Documenting means recording, member identification and after electronic signing of recorded file we store as evidence for public or court - as necessary. This issue is answered below in number 3. From my part I support link without password and the password should be entered at the prompt of conference for everyone. Tha password will define the role we play in the conference. But every button in the GUI are welcome.


This is something we can review. We do take confidentiality quite seriously. Until recently there was an issue in the VCS which prevented promoted hosts in a conference from sending invitations with the participant password in the hyperlink. This was caused intentionally because we did not want to send passwords to promoted users to help keep them confidential. While this did help keep conferences more secure, it presented a large usability problem for our customers: Promoted hosts were inviting users to conferences intentionally, but these users were unable to join because neither the host nor the participant had access to the password.

Our goal is to achieve a balance between accessibility and security, and I hope my explanation above gives some insight into our dilemma.

One possibility which you may use is the restricted registration feature of Nefsis. The hosts specifies email addresses they want to invite to a conference (these users do not need Nefsis accounts) and the users must follow a link in the invitation email to register for the conference. After registering the user will be sent a unique link that grants them entry to the conference. They will not be able to join through any other means, even if they know one of the passwords.

Restricted registration is currently available in Nefsis. Please see this section of our user guide for more information: Nefsis Invitations

<< < > >>
Reply to this Thread

NEED HELP?

Europe:   +44 (0) 870 224 0415  (09:00 to 17:30 weekdays, GMT)