eLandings User Manual

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Managing Operations

The eLandings system allows users to self-manage operations and users authorized to submit reports for those operations. In addition to registering new operations and users, the rights to view and edit reports may be granted and revoked.

Primary User

Each operation requires and allows for one primary user. When the operation is first registered, the user who creates the account becomes the primary and administrative user. The primary user is also the administrative user for the operation and cannot have his/her administrative privileges removed. An administrative user may change who is the primary user for an operation but the primary user cannot be disabled until that privilege has been changed to another administrative user. A person's account should be disabled if they leave the company.

Administrative Users

To provide security and control of user and operations management, only administrative users may authorize other users for operations.
As mentioned above, when an operation is registered the person who creates the account automatically becomes the primary and administrative user for that operation. With administrative privileges, the user can authorize other users within the operation and revoke their authorizations as needed. An administrative user can also grant administrative privileges to other users for an operation which allows to determine user roles.

Limiting a User's Access to Reports

A user's ability to view and edit reports is limited to the operations they are authorized for and the permissions related to their user account. The eLandings system allows administrative users to restrict access to only those reports that certain users create which have not been edited by someone else. Users that have these restricted privileges are known as Limited Users.

There are typically two situations where you might want to utilize the Limited User capability.

One is for a dock foreman or other users who are responsible for unloading catch from delivering vessels but who are not responsible for submitting fish tickets and landing reports. Limited users can create a new landing report when a vessel arrives and enter basic information like the vessel ADF&G number, date of landing, the CFEC and IFQ permits, etc. Office staff can come in later and fill in the itemized catch, grading and pricing information, and IFQ reports. Once the office staff begins to work on the landing report the limited user will no longer be able to edit or view that report.

Another situation where you might want to make someone a limited user is when you use an agent who is not an employee of your company. If they were not a limited user, they would be able to view all the landing reports for your operation. As in the instance above, if they are limited users they can only initiate and edit a landing report that they created for you as long as no one else from the company opens the report to make edits.

Read Only Users

Another way that administrative users can allow restricted access to reports is to authorize users as read-only users. The read-only users can view all reports for operations where they are authorized, but cannot make any edits. There are a number of reasons why you might want to have read-only users. 

One case is where a third party service organization needs to query your reports to provide you with summary information and advice. In this case they need to be authorized to view your reports, but have no need to update reports.

Another case is accounting personnel for your company who need landing report information to compile activity and financial reports. They, also, have no need to update reports.

 

  • No labels