Registration and user profiles Sample Clauses

Registration and user profiles. Prospective members of the VCoP can register themselves. To do so, they must go to the VCoP main page (xxxxx://xxxxxxx.xxxx.xxx.xx/index.php/en/) and click on “Register Today” as shown in the screenshot of Figure 2. If they already had an account, they could log in the same screen. Note that language can be changed at any time, including the log in or registration screen, and language preferences are respected until the user decides to change to another language. Currently, the VCoP is available in English, Spanish, Greek and German. In this report, screenshots of the English version will be shown. Figure 2: VCoP entry page. In it, users may register or log in using one of the four different available languages. Once the users select to register, several other screens must be followed in which they have to select username, password and provide their account details. The only mandatory fields are a full name and an email, but users may, if desired, provide many other details and personalize their profile. Registration is not completed until the account is approved by a Community Administrator. This was decided to avoid a potential attack based on the automatic creation of a large amount of users. User accounts could also be blocked at any time by Administrators, if some type of abuse is detected. Users receive an email both when they fill out all the required data and when their account is approved. In our case, we have customized the approval email to instruct users to follow the discussion forum of their preferred language (see later), so that they start interacting with other users. It should be noted that VCoP members have several profile planes: the most basic one, derived from Joomla, includes basic data like name, description, location, avatar, etc. (see Figure 3, left); a relevant plane, derived from EasySocial, includes information that can be used to implement social features. Particularly, users can declare their ID in some popular social networks, including Facebook, Twitter, Linkedin, or Skype. These can be used to propagate the content that users find interesting in the VCoP through these other systems, and hence attract new users to the VCoP (see Figure 3, right, for the configuration of one user -- the main author of this report). <.. image(Interfaz de usuario gráfica, Texto, Aplicación, Correo electrónico Descripción generada automáticamente) removed ..><.. image(Interfaz de usuario gráfica, Texto, Aplicación, Correo electrónico Descripción...
Sample 1
AutoNDA by SimpleDocs

Related to Registration and user profiles

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Registration Data Upon placing an order for Pilot Voice, and at subsequent times as requested by Pilot, Customer agrees to provide Pilot with its (i) true, accurate, current, and complete business name, (ii) physical addresses where Voice Service will be used, (iii) 911 registered address for each applicable endpoint, (iv) a designated Account Administrator, and (v) user email addresses, phone numbers, and any other requested data which may be necessary to administer its Voice Service account (the “Account”) (collectively, “Registration Data”). Customer represents and warrants that the information it provides is accurate, current, and complete, and agrees to promptly update any of the information if it changes. If Customer provides Registration Data that is false, inaccurate, not current, incomplete, fraudulent, or otherwise unlawful, Pilot has the right, in its sole discretion, to suspend or terminate the Voice Services and refuse any and all current or future use of all Voice Services by Customer, its business(es), affiliates and all users of its Account. Upon provision of all Registration Data and acceptance of Customer’s Service Order, Pilot may provide Customer’s designated Account Administrator and other Pilot Voice users with, as applicable, administrator or user web portal logins and other Account information. Customer is solely liable for any transactions or activities by it or any third- party that occurs on its Account. Customer shall immediately notify Pilot of any unauthorized use of its Account or if any other breach of security has occurred. In no event shall Pilot be liable for any unauthorized, third-party use of your Account.

  • Domain Name Registration If Customer submits a Service Order(s) for domain name registration services, the following terms shall also apply:

  • Registration Procedures In connection with the Company’s registration obligations hereunder, the Company shall:

  • LICENSING, ACCREDITATION AND REGISTRATION The Contractor shall comply with all applicable local, state, and federal licensing, accreditation and registration requirements or standards necessary for the performance of this Contract.

  • Registration Process In connection with the registration of the Registrable Securities pursuant to Section 4.1, the Company shall:

  • Registration of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Registration of Agreement The registration of License agreements should be done within 30 days of signing of agreement, the licensee/ lessee (registration fees, stamp duty etc to be fully borne by the licensee/lessee) and the duly registered documents to be submitted to Maha-Metro for records. Any amendment in the contract agreement, if required to be registered, shall also be registered within 30 days from the date of amendment and duly registered documents shall be submitted to Maha-Metro for record. In case the registration of the license/lease agreement /amendment is not done within the 30 days of signing of license/lease agreement/ amendment, it shall be treated as “Material Breach of Contract”. The Licensee will be given 30 days time to cure the defaults In case Licensee fail to remedify the default to the satisfaction of the Maha-Metro within the cure period, Maha-Metro may terminate the License agreement after expiry of cure period duly forfeiting the security deposit/ any other amount paid by Licensee.

  • Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-­‐to-­‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

Time is Money Join Law Insider Premium to draft better contracts faster.