Functionals Introduction

A 'functional' account can be used when there is a need to separate a business function from the name of a particular person performing that function, or where a number of people need to access the same account.  Examples of acceptable use include;

• College, School or Team contact address
• Event Specific accounts e.g. registration accounts
• Training/lab generic accounts
• Kiosk/data entry screens
• Scheduled task email accounts
• System administration accounts
• Batch Processing Account
• Data logging
• Special Purpose accounts e.g. Testing Accounts
• Inflexible working practices requiring generic logins 

All accounts within the University are subject to an Account Expiry Policy. Those creating and managing functional accounts should be familiar with this and keep this in consideration when creating accounts. Functional Accounts go directly to Suspention for a period of 30 days, before being archived.

The Account Expiry Policy is at this link: https://www.ed.ac.uk/information-services/about/policies-and-regulations/operational-policies/account-expiry