Overview

Administering an application in a complex computing environment, such as at U.C., Santa Barbara, can be daunting for a new administrator. This document is intended to present important information that new and experienced administrators may find useful in their work.

To begin with, an administrator should have an understanding of Com-Plete Userids and the elements of good password design, to help you and your staff better secure access to University data.

It's imperative that administrators know their departmental application in order to better administrate it. You need to be the expert on any "front-end" security (should it exist) for your application or system. You should have a basic understanding of the authorization process because you may be requesting access to other applications, or, deciding on access requests for the application you administer. If you are an application "owner", you may receive various security reports to help you manage your application. You need to know how to read and interpret these reports.

Finally, an understanding of procedures will help you interface with IS&C security administration.

Topics:

Who is This Guide For?
The Authorization Process - How it Works
Common Procedures

How to Request Access
How to Close Access
How to Change a User Profile
How to Have a Password Reset
Department Administrator Types
Everything You Ever Wanted to Know About a Com-Plete Userid
How to Become Expert on Your Application or System
Password Design Elements
Reporting a Security Breach
Security Reports
System Monitoring
Information Just For the All-In-One DSA
List of Security Group Assignments
Com-Pass Screen or All-in-One Menu
Chart of Account Department Codes
E-mail Nicknames


Who is this Guide for?

This Department Administrator Guide is intended to assist campus administrators, located in administrative or academic departments, who are responsible for OS/390, Com-Plete, Natural, or PL/1 applications, running on IS&C's Enterprise Server, located in North Hall.

If you are . . .

  • a Natural Application administrator or owner, or
  • a Department Security Administrator (for the All-In-One application), or
  • a "legacy" system administrator or owner, or
  • an accounts administrator for your department, or
  • a department contact who receives reports from IS&C, or
  • an executive, manager or supervisor interested in IS&C processes and procedures,

. . . then this Department Administrator Guide is intended for you.

The information contained within this Guide is not considered "sensitive" and is intended for public dissemination.

The Authorization Process - How it Works

For Com-Plete Userid billing. All Com-Plete Userids are billed to a Computer Center account. A request to set up a new Com-Plete Userid may require the IS&C Accounts Administrator to contact your department's account controller to authorize the creation of a new account and approve any allocation of funds to that account. A Com-Plete Userid cannot be activated unless a funded Computer Center account exists.

For linking a Com-Plete Userid to a Production Application. Each application running under Com-Plete has a registered owner known as a "Department of Record". For each department application there is at least one department administrator responsible for authorizing access requests from prospective users. Once formal authorization is received (normally by E-mail), IS&C security administration will proceed with the request. Access requests and department authorizations are filed for audit purposes (there are several access request forms available on the web, including the "Com-Plete Request" form and the "All-in-One Request" form). IS&C security cannot process an access request until approval has been received from the department of record.

For a Test Application. Each "TEST" application running under Com-Plete is administered either by the IS&C Financial Systems Manager or the IS&C Student Systems Manager. Normally, access to a TEST application is restricted to a developer. A developer may request access to a TEST application by contacting the appropriate IS&C Manager. If approved, the IS&C Manager will notify IS&C security administration to set up access.

For Adabas and Natural File Access. A request to link a Natural or Adabas file to an application or system is normally authorized by the department that is billed for the file.

For access to a OS/390 Partitioned Data Set. A "Partitioned Data Set", or PDS, is a special type of library that may contain, for example, JCL, Natural code, or data. Many of these libraries have a registered departmental owner and are secured by RACF. If you are a department administrator responsible for one or more OS/390 Partitioned Data Sets, IS&C security administration will be in contact whenever an access request is received. Once formal authorization is received (normally by E-mail), IS&C security administration will proceed with the request. Access requests and department authorizations are filed for audit purposes. IS&C security cannot process an access request until approval has been received from the department administrator.

Common Procedures

As a department administrator, you should to be familiar with some of the most common IS&C security procedures.

How to Request Access

To open a Com-Plete Userid requires that an applicant submit a request form. The request form to be used differs somewhat from application to application. To determine which application form to use, you need to be able to answer these questions:

  • What is the Log-on name of the application or system? (examples: STAR01, PYLV01, etc.)
  • What is the common name of the application or system that you believe you need access to (examples: Payroll Leave Reporting, Requisitions Express, Star, etc.)?
  • Which department is the "Department of Record" for the application, system, or utility that you need (this is important, for all approvals for access must come from the department)?

Once you have the answers to the above questions, the general application process is as follows:

  1. The applicant applies for a service. The application form may differ depending on the desired service (Hint: refer to the Forms Lookup Table ).

    For example:

  2. The appropriate application form is submitted..

  3. The application administrator in the "Department of Record" reviews the request.

  4. If the request is approved by the application administrator it is forwarded to IS&C. IS&C staff will:
    • coordinate with the IS&C Accounts Administrator to open a Com-Plete account for the new user (a funded account is required before a Userid can be set up);
    • set up a Com-Plete Userid (this enables the user to logon to Com-Plete);
    • link the user's Userid to the approved application (this enables the user to logon to the application); and
    • notify the user and requester once the Userid is ready.
    • Normally, processing to set up a Com-Plete account and Userid takes about 10 working days once IS&C security administration has received authorization from the "Department of Record".

  5. The user logs on to Com-Plete with the new Userid. The user can then logon to any approved applications (Note: most applications have internal security administered by a department administrator and the department will set up application permissions. Questions regarding specific permissions within an application should be addressed to the "Department of Record").

How to Close Access

Deletion of a Com-Plete Userid is normally a two step process: the Userid is deleted from Com-Plete and the Computer Center account is closed (Note: a Computer Center account should remain open if other Computer Center services (such as email) are to remain in use; in such instances only the Com-Plete Userid is deleted).

As a Userid is normally assigned to an individual, a department administrator should try to anticipate personnel changes (if possible) and arrange to set up a new, replacement, Userid to minimize disruption of work.

A Userid can be deleted and/or an account closed for any of the following reasons:

  • By request. The preferred method of deleting a Userid is by request from a department administrator upon employee separation or termination. Upon receiving a request, IS&C security administration will delete the Userid and will coordinate with the IS&C Accounts Administrator to arrange for the closure of the account. Please use the "Request for Com-Plete Service Delete Form".
  • Account closure. When a department account administrator initiates a request to close a Computer Center account, IS&C security administration determines if there is an existing Com-Plete Userid tied to the account. If there is an existing Userid tied to the account, confirmation to close the account and delete the Userid is requested (in order to avoid the closure of an account with a Userid that should remain open).

 

How to Change a User Profile

When a Com-Plete Userid is initially set up, a User Profile consisting of Account, User Name, Output Bin and Destination is created. The User Profile has many uses, including:

  • Account: accounting information is used for billing on-line access and batch jobs.
  • Destination: output is normally routed to the printer specified as the users default printer destination (Note: the printer destination can be changed by the application software).
  • Output Bin: bins are located in North Hall, and any printed output directed to UCSBMVS.R0 will be placed into the bin specified as the users bin.
  • User Name: often used to identify the owner of printed output.

Current settings for a User Profile are displayed on any Job Submission screen. The user profile may be need to be changed if there has been:

  • An account change; or
  • A change in the printer; or
  • A change in the user's name; or
  • A bin change.

Send an Email note to isc.security@isc.ucsb.edu to request changes to a User Profile. On this note detail any user profile change you wish to make.


Department Administrator Types

IS&C security distinguishes among types of administrators based on function. These 3 types include:

    • an application owner (registered in the Predict data dictionary)
    • the day-to-day administrator of a department application
    • the accounts administrator for your department.

In practice, a large number of departments have chosen to combine these 3 functional types into one individual, who is often the accounts administrator (these departments have chosen a "1 tier" approach, the least complex). Many such departments do not own applications themselves, but apply to other departments that do.

Some departments combine the functions of an application owner and day-to-day administrator into one individual, but separate those duties from a departmental accounts administrator (these departments have chosen a "2 tier" approach). These departments have decided that a certain amount of specialization is required to manage budgets as opposed to administering a department system (such as the Accounting owned APEX system).

A small number of departments have delegated these 3 functional types among different employees (these departments have chosen a "3 tier" approach, the most complex). In part splitting the "ownership" function from the "day-to-day" administrative functions is necessitated by the workload required for maintenance (such as for the Registrar owned STAR01 system).

However these functions are assigned, care must be exercised to avoid miscommunication within a department, or, between a department and IS&C, or between departments. As an department administrator you should know how your particular department distributes (or combines) these functions within the department.

    1. Application Owner. An application owner is responsible for determining access permissions for department owned systems (if any).
    2. Each Natural application has one or more registered owners (entered in Predict). Specifically, an application owner is responsible for:

        • approving Com-Plete access requests;
        • denying Com-Plete access requests;
        • modifying Com-Plete access permissions;
        • determining the permission level of a Com-Plete request, such as read only, or, update;
        • determining which Natural screens a user may access within the application;
        • submitting requests to revoke Com-Plete access, as when a user terminates or separates;
        • reviewing change/enhancement requests from developers, such as file linkages;
        • receiving and reviewing various security reports;
        • delegating security duties to a "day-to-day administrator" as appropriate;
        • coordination with IS&C security administration.

      If you need to know who is the registered application owner for a particular application, contact IS&C security administration.

    3. Day-to-Day Administrator. The day-to-day administrator is responsible for implementing access decisions made by application owners (for departments that own systems).
    4. Usually, the day-to-day administrator is responsible for:

        • using an application's "front-end" security (if it exists) to
        • - add a user record
          - change a user record
          - review a user record
          - purge or delete a user record
          - run reports
          - configure the screens a user may (or may not) view
          
        • submitting Com-Plete access requests on behalf of a user;
        • submitting Com-Plete requests to revoke access, as when a user terminates or separates;
        • user training;
        • coordination with IS&C security administration.

      If you need to know who is the day-to-day administrator for a particular application, contact IS&C security administration.

    5. Account Administrator. The account administrator is responsible for departmental financial decisions related to the accounts.
    6. Usually this involves:

        • reviewing monthly billing statements from IS&C;
        • opening Com-Plete (and other Computer Center) accounts;
        • closing Com-Plete (and other Computer Center) accounts as when an user terminates or separates (exercise care, so as to not close an account for an active Userid);
        • coordination with department application owner;
        • coordination with IS&C accounts administration;
        • coordination with IS&C security administration.

      If you need to know who is the accounts administrator for a particular department, contact the IS&C Accounts Administrator.


Everything You Wanted to Know About a Com-Plete Userid

A Userid is a unique identifier that enables a user to logon to Com-Plete, thereby accessing various computing services for which the user has been authorized.

Spelling. The term "userid" has several valid spellings, which you may encounter, including, for example, User ID, USERID, Userid, and User-ID.

Purpose. A Userid is a simple way to authenticate a user to Com-Plete.

Role of IS&C security administration. IS&C security administration is responsible for setting up a Com-Plete Userid. In order to maintain an audit trail, all Com-Plete Userids are kept for a minimum of 7 years after an employee separates or terminates.

Userid Types:

Personal. A "personal" Userid is the most popular kind of Userid assigned. It is assigned to one particular individual for their exclusive use. This type of Userid has the following restrictions.

  • A personal Userid is assigned to a particular user (the owner).
  • The owner may not transfer the use of this Userid to another user.
  • The owner is responsible for any abuse or misuse of computer access that may arise from the use of their assigned personal Userid.
  • Upon separation or termination, IS&C security administration must be contacted by the Department Administrator to close the Userid.

Shadow. A user may have more than one Userid, if their work requires it. Each additional personal Userid is known as a "shadow" Userid. This type of Userid has the following restrictions:

  • A shadow Userid is assigned to a particular user (the owner).
  • A shadow Userid may be "loaned" to another user by the owner (if so, the owner is responsible for training the other user).
  • The owner is responsible for any abuse or misuse of computer access that may arise from the use of the shadow Userid.
  • Usually, this type of Userid is used for department owned applications (cannot be used to access another department's data).
  • Upon separation or termination, IS&C security administration must be notified to close the Userid.

Generic. Several individuals may use a "generic" Userid assigned to a departmental position. Most positions that utilize temporary or casual employees benefit from this type of Userid. This type of Userid is subject to some restrictions.

  • A generic Userid must be assigned to a department contact, who becomes the owner of the Userid.
  • The department contact is responsible for training the users of the Userid.
  • The department contact is responsible for any abuse or misuse of computer access that may arise from the use of the generic Userid.
  • Usually, this type of Userid is used for department owned applications (cannot be used to access another department's data).
  • This Userid is transferable, that is, multiple users may use it in the course of their normal duties.
  • Upon separation or termination of the department contact, IS&C security administration must be notified to either close the Userid, or, transfer ownership to a new department contact.

How to Become Expert on Your Application or System

Did you know that there are almost 150 administrative applications currently in use, with new ones under development! If you are an application administrator you are empowered to make decisions regarding access requests and permissions. IS&C security is here to assist you in administering your application, but you must know your application.

Here are some ways to learn more about your application or system:

  1. System Documentation. If formal documentation exists for your system, you are fortunate! Study it! If no formal documentation exists for your system, start a binder for each system or application that you administer. Keep this binder in an easy to reach place. Collect any notes, screen samples, etc., in your binder relevant to your system. Should you transfer or separate from the department pass over your binder(s) to your successor. Keep any confidential information related to your application in a secure location.
  2. On-line Help. If your system has an on-line help system, become familiar with it!
  3. Training. Arrange for training on how to use your application (if any formal training is available, such as for the All-in-One application). If your application has its own internal security component, additional training may be required.
  4. Seek those who have experience with the application. Seek out those individuals in your department that have used your application or system ... their experience may be invaluable.
  5. The "Job Submission" screen. As an administrator, you may need to know how to read and understand a "Job Submission" screen, also known as a "RJE Submit" screen. "Job Submission" screens are often used, for example, to submit jobs that print hardcopy reports. Displayed below is a sample "Job Submission" screen (your "Job Submission" screen may differ slightly).

 

    Four elements of a "Job Submission" screen are set up by IS&C security administration when a user is added to Com-Plete, including:

    • Output Bin. This is the Bin or Locker where printed output will be distributed if printed at the Computer Center in North Hall. Some departments have reserved special lockers for their output.
    • User's Name. The name of the user.
    • Account. The Computer Center account being charged for the "Job Submission".
    • Destination. The printer where output is to be routed.

    Taken together, these four elements are known as a User Profile. As an administrator you can coordinate modifications to a User Profile for a user in your department (such as changing the printer Destination). See the section named Change User Profile for more information on how to submit such requests.

    The remaining items on a "Job Submission" screen (such as CPU Time, Print Lines, Message Class, Copies, and Forms) are programmatically controlled by the application itself and are not maintained by IS&C security administration.

    Detailed information regarding all the elements of the "Job Submission" screen and Job Control Language (JCL) is available in this document on JCL.

  1. Security groups. Access to your application or system is usually accomplished by placing a user into a security group. All applications have at least one such group, others may have two groups (one for "read only" access, the other for "update", for example), and other applications may have many security groups. As an application administrator, do you know the name and function of the security groups for your application? If you don't, contact IS&C security administration for a thorough review of these security groups.
  2.  

  3. Account administration and application administration. Department account administrators are responsible for the administration of Com-Plete accounts. Account administrators receive monthly IS&C Billing reports, monitor expenses (such as connect charges), and approve the opening or closing of Com-Plete accounts. The IS&C Accounts Administrator works closely with department account administrators to resolve any questions or concerns regarding accounts.
  4. Application administrators are responsible for approving the setting up (or closing down) of Com-Plete Userids, for authorizing access to an application, for application security and receive IS&C Security reports. Such administrators usually know a great deal about the data, files and security structure of an application.

    In many departments, the functions of the account administrator and application administrator are highly specialized with one user focusing on accounts, and another user focusing exclusively on application administration. In other departments, these functions are combined and a single user acts as both the account and application administrator. As a department adminzistrator you should know whether these functions are specialized, or, combined. If these functions are specialized, coordination in your department is required between the accounts administrator and application administrator to ensure that a Computer Center account is not closed for an active Com-Plete Userid.

  5. Application-level security. A number of departmental applications have their own built-in security sub-system, administered by a department user, that is totally separate from the security systems administered by IS&C security administration. Applications or systems with such a security sub-system are considered to have "application-level" security. An "application-level" security sub-system supplements (but does not replace) any security systems employed by IS&C security.
  6. Generally, application-level security allows a department administrator to:

    • set up access permissions for an application (such as what screens a user may or may not view);
    • modify access permissions for an application (such as upgrading a user from "read-only" access to "update" access);
    • display existing user permissions for an application;
    • purge users from the application.

    IS&C security administration is not empowered to maintain any "application-level" security. Consequently, IS&C security administration can only provide minimal assistance should any questions or problems arise with "application-level" security.

  7. OS/390 Libraries. Does your department use OS/390 libraries for submitting jobs for a system you administrate? If you are an administrator you should know how to identify these libraries and how they are secured.
  8. If you need further information, contact IS&C security administration for a quick orientation.

  9. Monitor Access. To be an effective administrator means that you will need to monitor who has access to your application or system. IS&C security provides these Security Reports to help you monitor access.


Password Design Elements

A Password is a string of alpha-numeric characters used in conjunction with a Userid to logon to Com-Plete. A password is used to verify that an individual is the legitimate user of a Userid.

User Responsibilities

  • To manage their password.
  • To ensure the confidentiality of a password.

Responsibilities of a Department Administrator

  • To encourage good password design. As an application administrator, you can help your staff to create good passwords!
  • To discuss password design with each new employee as part of their orientation.

Responsibility of IS&C Security Administration

  • To set up an initial one-time logon password for Com-Plete.
  • To respond to user questions regarding password maintenance.

The following tables summarize the enforced and recommended password design elements of Com-Plete.

Com-Plete Password Elements
Password Design Elements Enforced by Com-Plete
Password has a Maximum 8 characters in length
Lower case automatically converted to UPPER CASE
All letters allowable (A,B,C,D,E,F,G,H,I,J,K ...,U,V,W,X,Y,Z)
All numbers allowable (0,1,2,3,4,5,6,7,8,9)
NOT ALLOWED: hyphen ( - ) in password
NOT ALLOWED: blank in password
NOT ALLOWED: special characters (* , &, %, etc.)

Password Design Recommendations
Password should be between 6 to 8 characters in length
Password should mix numeric and alphabetic characters
Password should NOT be the same as your Userid
Password should NOT be your name (or spouses', friends', pets', childs', etc.)
Password should NOT be a geographic name
Password should NOT be a word in the dictionary
Password should be changed periodically
Password should be memorized, not written down

Reporting a Security Breach

Contact your Manager, IS&C Security Administration, or Internal Audit to report it.

Security Reports

As an administrator you may receive from IS&C security administration several different security reports to assist you in administering an application. In addition, there is a security report you may generate yourself at your convenience.

(1) Department "Security Report"

If you are a registered application owner, you will receive a Department "Security Report" for each application you administer (your name appears as an "APPLICATION AUDITOR"). The purpose of the "Security Report" is to show who has access to the application that you administer. Users can be linked to your application as an individual, or as a member of a group of users.

This report is generated by IS&C security and is distributed quarterly. Enclosed with each report is a cover letter that highlights the elements of the report. Should you need clarification regarding any portion of the report, contact IS&C security administration.

Displayed below is an abridged sample of a fictitious "Security Report" for an application named LIMA01.

(2) "Current Employees with Com-Plete Access" Report

A department receives the "Current Employees with Com-Plete Access" report if the department has at least one individual with an existing Userid. The purpose of this report is to list all users in your department that have access to Com-Plete. This report is intended to help you (1) administer your department's access to university data, and (2) administer your department's computing expenses.

This report is generated by IS&C security administration twice a year. Enclosed with each report is a cover letter that highlights the elements of the report. For each employee the report prints Name, Userid, Phone, department code and Job Title. There are 4 check-boxes:

    • Active: to be checked if the employee is still actively employed in your office.
    • Transfrd (Transferred): to be checked if the employee has transferred to another UCSB department or office.
    • Separtd (Separated): to be checked if the employee has terminated employment.
    • Mismatch: to be checked if an employee's assigned Userid is being used by another employee.

Should you need clarification regarding any portion of the report, contact IS&C security administration.

Displayed below is an abridged sample of a fictitious report for the Meteorology Program (Note: this program does not exist at the university!).

(3) "List of Datasets Billed" Report

This report displays all OS/390 and Adabas data sets being charged to a specified account. This report is a valuable tool that will help you track certain computing expenses.

As a department administrator, you may run this report at any time. To run this report:

Logon to the Natural application named UTILITY. This is a special library containing public utilities for Com-Plete and Natural users.

On the Main Menu, find the function named Submit 'Billed Datasets' Report.

Input the code for that function; press Enter.

A "Job Submission" screen will be displayed (named "Submit List of Datasets Billed"). Your screen should resemble the below example.

Follow the instructions as indicated on this screen (press PF4 to submit). The report will be printed at the "Destination" displayed.


 

The printed report generated by you will resemble the following example (note, your report may differ greatly, depending on the number of data sets you have).

  1. Should you need clarification regarding any portion of this report, please contact Donn Howell at Information Systems & Computing.

(4) Special Request Reports

Selected requests for security reports will be honored by IS&C security administration on an case-by-case basis, such as:

  • A request to review User Access Permissions to Com-Plete, Natural, or legacy applications.
  • A request to review User Default Settings, such as account, printer assignment, or output bin.
  • A request to review User Billing, such as what account a Userid is being charged to.
  • A Security Review for a department. A department review can be tailored to your department's specific needs. For example, it may involve researching:
    • A user's RACF access permissions;
    • Natural applications linked to the user;
    • Any Legacy applications that are linked.

If you might be interested in a special report, contact IS&C security administration.

System Monitoring

Monitoring of the OS/390, Com-Plete and Natural computing environments is a normal function of IS&C security administration.

Information Just for the All-in-One DSA

List of Security Group Assignments.

As a DSA, you can list security group assignments for your department on-line. There are 2 ways to generate this list:

By use of a "direct command":
  • Position your cursor to a Direct Command line;
  • Type the command AU SG; press Enter.
  • The members of your All-in-One security groups are displayed on the "Browse Security Group Members" screen.

By use of menu functions:

  • From the "Main Menu" (of "Financial Systems Functions All-In-One" system) input AU in the "Code" field; verify that the department code in the "Dept" field is correct (if not, change it to the department code you need); press Enter;
  • The "Financial Systems Authorization System" "Main Menu" is displayed. On this screen input SG; press Enter.
  • The members of your All-in-One security groups are displayed on the "Browse Security Group Members" screen.
If you need a hardcopy listing of the security group assignments, you will need to print each page manually.

If you are a DSA responsible for multiple departments, type additional department codes in the Dept Code field on the "Browse Security Group Members" screen to view security group assignments for other department codes.

Com-Pass Screen or All-in-One Application Menu

The Com-Pass screen and the Application Menu are the two methods currently available for accessing Com-Plete. Technically known as a "user-interface" each differs widely in its appearance and functionality. If you are a Department Security Administrator (DSA) you may need to decide which user-interface is appropriate for an applicant.

* The Com-Pass screen is the default user-interface to Com-Plete (view sample) . Most users of Com-Plete will see this screen after their logon.

* The Application Menu is a featured user-interface available for users of the All-In-One Financial System (view sample) (Note: this user-inteface is available only to an All-In-One user).

When an All-In-One request form is received:

  • A new Com-Plete user is set up with the Application Menu;
  • An existing Com-Plete user is automatically converted from the Com-Pass screen to the Application Menu.

Exceptions. An All-In-One user will not be converted to, or, set up with the Application Menu if:

  1. A Department Security Administrator specifies a preference for the Com-Pass menu in the "Comments" portion of the All-In-One Access Request form; or
  2. The user must access another application that is incompatible with the All-In-One system; or
  3. The user has access to more than 10 Natural applications (this is a built-in limit to All-In-One).
Chart of Account Department Codes

The "Chart of Account" department codes are administered by the General Accounting section in Accounting and Financial Services . These department codes are 4 characters in length. All departments at U.C.S.B. have at least one "Chart of Account" code.

Role of All-In-One Department Security Administrator (DSA).
  • A DSA must know all of the "Chart of Account" department code for their department;
  • A DSA is responsible for providing the "Chart of Account" department code (or codes) on the All-In-One Access Request Form for each applicant.
  • A DSA is responsible for creating a user record for each "Chart of Account" department code

    (Hint: if a user is to be authorized for multiple department codes, set the user up as you want for one department code. For any additional codes, (1) modify the department code, (2) input A for "Action" (Add a Record); and (3)press Enter. The user now has been authorized for another department code).

Role of IS&C Security Administration.

  • To set up a DSA for each department code).

Role of Accounting and Financial Services.

  • This office is responsible for maintaining the "Chart of Accounts". Additions to, deletions from, name changes, or collapsing of categories are the responsibility of the Accounting and Financial Services department.
  • Questions regarding your department codes should be directed to Accounting and Financial Services.

E-mail Nicknames

All users of the All-In-One Financial System are required to have a current, valid, E-mail address and a corresponding E-mail nickname.

As a DSA, it is your responsibility to:

  • Add a new user to All-In-One, including the E-mail nickname as provided to you by IS&C security administration.

  • Inform IS&C security administration when a user's E-mail address changes. IS&C security administration will coordinate changing directory information and create a new E-mail nickname. Failure to inform IS&C of an address change may result in an undeliverable E-mail message.

  • To change the user's E-mail nickname in the All-In-One system when requested by IS&C security administration. Failure to change a user's E-mail nickname may result in a "No match found on nickname" error.

  • Purge department All-In-One users when a user leaves the department. Failure to purge a user record from All-In-One may cause a "No match found on nickname" error if the user was a department approver or releaser and had been deleted from the E-mail directory.

 

For assistance or further information please contact webcontact@ucsbuxa.ucsb.edu .

Last Modified: CGH,01/30/02