.. _forced-authorization-codes:


Introduction to Forced Authorization Codes (FAC)
--------------------------------------------------

.. index:: Feature;Feature Forced Authorization Codes (FAC)
.. index:: Forced Authorization Codes (FAC) (Feature)


.. _20.1.1|VOSS-592:



The Forced Authorization Codes (FAC) feature provides the ability to use codes to authorize certain
types of calls as setup in the dial plan. For example, to make an international
call, a code might be shared with people who need it and they can enter the code
after dialing their call in order to authorize this.

To use FAC, the deployed dial plan must to be set up in a way that enables
the codes to be used. For more details on the use of FAC and CUCM functionality, refer to the Cisco documentation.

VOSS Automate provides full support for FAC, from setting up the dial plan elements
to the management of the codes themselves. Refer to the *VOSS Automate Provider HCS
Dial Plan Management Support Guide* for more details on managing the dial plan
elements.

VOSS Automate supports the provisioning of FAC using two methods:

* :ref:`fac-device-models` - this basically mirrors the setting up of codes in
  the Unified CM. It uses the device model in VOSS Automate and allows you to add/mod/del
  codes for a given cluster. 
* :ref:`fac-code-management-voss` - this feature helps to improve the usability of
  FAC codes and to manage consistent FAC codes across clusters in an orchestrated
  way. It provides the ability to define which authorization levels you require and
  to provide text along with the code to help administrators understand the purpose
  of the different levels as implemented in the dial plan.

The method to use depends on your requirements, but generally the VOSS Automate FAC
Code Management method is likely to be a better overall fit.

The appropriate option(s) you want to use should be included in your menu designs
for the required roles for administrators to access. You may want to use both
methods if you need to manage FAC codes per cluster in some cases, and across
clusters for other cases. Any existing codes synced into VOSS Automate will appear in
VOSS Automate and can be managed via either method.