Keep Permissions Simple
Since NextPage
hosts no content, the presence of NextPage does not either increase a user’s ability to read or write a file. Identities and permissions affect only:
The NextPage model for identities and permissions is extremely simple.
Administration
During a pilot or trial phase, most organizations find it most convenient to administer identities manually through the NextPage admin console. When it comes time to roll out tens of thousands of users for production, NextPage can take identities from your organization’s pre-existing directory system.
Secure Identity
Each end-user machine that has the NextPage Client Agent maps itself to a user identity. When it first attempts to do so, the Enterprise Service verifies the mapping through one of two methods: an email confirmation that the end user must click in order to prove access to his own email account, or silent transmission of a pre-agreed token string. The former is more common during a trial or pilot phase; the latter is more common in production since it does not involve any user input.
Multiple Machine Support
A single user identity can be associated with multiple machines. When a second or third computer is tied to an existing user identity, the same mechanisms can be used to verify the new mapping.
Simple Permission Model
Your organization has already invested deeply in determining who can see what in the pre-existing document infrastructure, whether that consists of end-user hard drives, user directories on the network, shared drives, collaborative spaces or formal document-management systems. NextPage does not change any of that; all your organization must now decide is who can use what file classifications.
